Hamloy alternatives

Every fact about another tool here comes from its own site or docs, read on 10 October 2026. Where we wrote a full comparison, it's linked.

You want it open source, or to run it yourself

Hamloy is closed and hosted; there is no version to run yourself.

• Beads: an issue tracker for coding agents that keeps a dependency graph in a Dolt database in your repo, with a bd command line, atomic claims and a list of what's ready. MIT. Hamloy vs Beads.
• Backlog.md: every task a Markdown file in the repo, a board in the terminal and one in your browser on your own machine, for agents through the command line or MCP. MIT.

You work offline, or want the list in the repo

Hamloy needs a network: your agents reach it over the internet.

• A TODO.md: free, plain, offline, and reviewed with the code. Hamloy vs a TODO.md.
• Task Master: tasks in .taskmaster/tasks/tasks.json in the repo, readable by any agent.
• Beads and Backlog.md, above.

You want a plan written from a spec

Hamloy calls no model of its own; your agent writes the tasks.

• Task Master reads a PRD and writes tasks with dependencies, subtasks and complexity scores. Hamloy vs Task Master.
• Kiro, an agent with its own IDE, turns a feature into a spec: requirements, a design, and a tasks.md of tasks it can run, independent ones at the same time. It has a free plan; paid plans start at $20 per user a month (pricing).

One agent, and you're at the terminal

Hamloy is built for several agents and a person who isn't always watching. With one session at a time, you may not need it.

• Claude Code's own task list keeps the steps of the work in front of it, on your computer, and comes with Claude Code. On newer models you turn it on yourself. Hamloy vs Claude Code's own to-do list.
• A TODO.md, above.

A team plans its product in a tracker

Hamloy shares a project with other people on Pro, but it has no cycles, roadmaps, triage or reports.

• Linear, "the product development system for teams and agents", with an MCP server and agents you delegate an issue to. Hamloy vs Linear.
• GitHub Issues, free with every repository, closed by the pull request that fixes it, and assignable to Copilot, Claude or Codex on paid Copilot plans. Hamloy vs GitHub Issues.

Both work beside Hamloy: the team's issues there, your agents' working list in Hamloy.

When Hamloy is the one

If none of those reasons is yours, and you run two or more agents at once, across Claude Code, Codex, Cursor or Claude, Hamloy is built for that: one board where you see what each is on and what it did, questions and requests for you, a claim on every task so no two agents take the same one, messages between agents, and done followed through git (why a shared list).

The rest are compared side by side in the best task trackers for AI agents.