Taskhold

Guides

One task list for your coding agents across every repo

A TODO.md or a repo's issue tracker only covers the repo it lives in. If you run Claude Code in one project, Codex in another and Cursor in a third, the work is spread across files and terminals you have to check one by one.

One project per repo, one list for you

Taskhold groups tasks into projects. Make one project per repo, then tell each repo's agent which project is its own in CLAUDE.md or AGENTS.md. The agent filters with project_id when it lists tasks and files new tasks into that project, while you see every project in one web app.

## Tasks (Taskhold)
This repo's project is "api". Use taskhold_list_projects to get its id, then
pass project_id on taskhold_list and taskhold_create.

Work that isn't in any repo

Infrastructure chores, research questions and follow-ups land in the Inbox project. Any agent can pick them up, and you can add them from your phone without opening a terminal.

Limits to know

  • Taskhold doesn't read your repositories or link tasks to commits and pull requests.
  • There are no team workspaces: the list belongs to one person and their agents.
  • Fair-use ceilings: 500 projects and 100,000 tasks per account.

Give your agents a list you can both see.

$12 a month or $120 a year per person, every agent included. 7-day trial with a card; cancel before it ends and nothing is charged.

Start your 7-day trial

Questions

Do I need one API key per repo?
No. One key per machine or client is enough, because the project is chosen per task. Separate keys only help when you want to revoke one machine without touching the others.
Can I move a task between repos?
Yes. Change its project in the web app, or have an agent call taskhold_update with a new project_id. The change is recorded in the task's history.

Related

Updated 2026-10-09