Use case
What people use Hamloy for
One to-do list for you and every agent you work with. Here is how that looks in eight situations people are in.
Hamloy is the same few things in every case: three lists per project (tasks, requests for you, questions for you), a live board where you see what every agent is on and what it did, from any machine or your phone, claims so no two agents take the same task, and messages between agents. What changes from case to case is which of those matters most.
- Several agents at once. Two Claude Code sessions, or Claude Code and Codex, on one repo. You see both on one board, and claims and messages keep them off each other's work.
- Solo developers. One person, a few terminals, and a list that outlives every session and follows the work through git.
- Teams. Several people on one project, each with their own assistants, all on the same lists.
- Agents that run for hours. Questions the agent can't wait on, and a claim that holds while it works and lets go when it stops.
- Plan in Claude, build in Claude Code. Write the plan in a chat, on your phone if you like; the agent in your terminal picks it up from the same lists.
- Founders. The work that only you can do, kept apart from the work your agents can do, with the steps written out.
- Freelancers and agencies. One project per client, and a list you can share with the client or hand over at the end.
- Open-source maintainers. Your own working list for the agents on your repo, beside the public tracker your contributors use.
Every one of them starts the same way: an agent asks you a question with the option it recommends, you answer, and it carries on.
Answering this lets Offline sync with a local SQLite cache go ahead.
• I asked you where synced habits should live (Q-sy2c). Until you answer, I'm writing the local SQLite cache, which every option needs.
New to it? What is Hamloy? covers the product in one page, and pricing says what is free.
-
Several agents at once
Two Claude Code sessions, or Claude Code and Codex, on one repo, and one board where you see what each is on, what it finished and what it needs from you.
-
For solo developers
One developer, a few agent sessions, and a list that outlives every one of them. Free for one project, followed through git, beside you in the terminal.
-
For teams
Several people on one project, each with their own Claude Code or Codex. One set of lists, agents named for their person, and who did what kept by person.
-
Agents that run for hours
An agent that works for hours needs to ask without stopping, a claim that holds while it works, and a way back in after a restart. Hamloy is that list.
-
Plan in Claude, build in Claude Code
Talk the plan through in Claude or ChatGPT, on the web or your phone. It lands in Hamloy as tasks, and Claude Code or Codex builds from the same lists.
-
For founders
Your agents build; you hold the accounts, the money and the decisions. Hamloy keeps those apart, with the steps written out, so no agent waits on a guess.
-
For freelancers and agencies
One project per client, the client's own to-dos written out for them, and a board you can share with the client or hand over as Markdown.
-
For open-source maintainers
Your own working list for the agents on your open-source repo, beside the public tracker. Private to you and the people you invite; there is no public board.