TL;DR: have each agent write its plan as steps, report "step N of M" as it goes, and block with a question when it needs you. Put all of that on one board that updates live. I built this into Taskhold, a task list I share with my agents, but the habits work with any tool your agent can call.

Why not just watch the terminals?

Because there are several of them, they scroll, and a question an agent asked twenty minutes ago looks exactly like the output around it. A per-session todo list helps inside one session, but it ends with the session and lives on one machine. I wanted one view across agents, repos and machines, that I could also check from my phone.

What should an agent report?

Four things, and only four:

1. A plan as ordered steps before it starts. In Taskhold that's one MCP call, taskhold_plan, which turns the task into steps.
2. Progress as it goes: either a percent or "N of M", plus one short line about what it's doing right now (taskhold_progress). Steps beat percentages; agents are much better at "finished step 3 of 5" than at guessing 60%.
3. Blocked, with a question when it needs a decision, access or information (taskhold_block).
4. Done, with a summary of what changed (taskhold_complete).

What does the board show?

One card per task in progress: a progress bar split by step, which agent is on it, how long it has run, an estimate of time left, and the current step's message. Blocked tasks go to the top with the agent's question and a reply box. Finished tasks drop into a "recently done" list, and there are optional desktop notifications for blocked and finished.

How does the agent get my reply?

It asks "what changed since my last check?" with taskhold_updates, which takes a cursor and returns only what the person changed: replies, new tasks, priority changes. The agent calls it between steps, so I can steer it mid-task without stopping the session.

How accurate is the time-left estimate?

It's deliberately simple: time elapsed divided by the fraction done. It stays hidden until the agent is at least 5% in and 30 seconds have passed, because before that it's a guess, and a wrong number is worse than none.

How do you know an agent died?

Liveness, not the bar. Each card shows whether the agent is live (reported in the last 2 minutes), quiet, or stale (nothing for 15 minutes). A stale card at 90% usually means the session ended and the task needs someone to pick it back up.

How is it built?

Every change an agent or person makes (create, status, progress, note, edit) writes a row to an events table, and the row id is the cursor for everything. The board streams new rows over server-sent events with an in-process wake for instant updates, a 3 second poll as a backstop and a 15 second ping so proxies keep the connection open. One gotcha if you do SSE from Next.js: its compression buffers the stream unless you send Cache-Control: no-transform; X-Accel-Buffering: no handles nginx.

How do I set it up?

In Taskhold you create a setup URL in Settings and paste it to your agent with "set this up". The markdown it fetches contains a fresh API key, the MCP config for that client (Claude Code, Cursor, Codex, Windsurf, VS Code, Gemini CLI) and a short rules snippet telling the agent to plan, report progress and block with questions. It's $12 a month with a 7-day trial.

If you don't want another tool, add this to your CLAUDE.md or rules file and you'll get most of the habit inside a single session:

Before starting a task, write your plan as 3 to 7 numbered steps.
After each step, say "Step N of M done: <one line>".
If you need a decision from me, stop and ask one specific question.

What do you use to keep track of agents running in parallel? I'd like to hear what works for you.

Originally published at taskhold.com.

If Claude used to show a checklist while it worked and now doesn't, nothing is broken. The list is filled by Claude calling task tools, and on newer models Claude Code no longer gives it those tools unless you ask. If you want progress you can see from outside the terminal, Taskhold's live board shows each task's steps as the agent reports them. More in Claude Code's tasks compared, Taskhold for Claude Code and seeing what your agent is doing.

The fix

Set the variable when you start Claude Code. The docs say this provides the task tools on every model and every provider:

CLAUDE_CODE_ENABLE_TODO_TOOLS=1 claude

# or for every session, in ~/.zshrc or ~/.bashrc
export CLAUDE_CODE_ENABLE_TODO_TOOLS=1

Naming one of the tools also turns them on for that session, for example claude --allowedTools TaskCreate, or listing them in --tools. Background sessions started from agent view and cloud sessions get the tools on every model without any setting.

Why the default changed

Claude Code's tools reference gives the reason: newer models keep track of multi-step work without a written checklist, and the tools' definitions and reminders take up context on every turn. So the list is off where it adds the least, and you can opt back in when you want to see the plan.

Other reasons the list looks empty

• Claude hasn't made a checklist yet. Ctrl+T toggles the view, and with nothing in the list the toggle has no visible effect.
• The view shows up to five tasks at a time, so a long plan looks shorter than it is.
• You're looking at /tasks. That lists background shells and subagents, not Claude's checklist.
• A model ID Claude Code doesn't recognize, such as a custom name behind an LLM gateway, is treated like a newer model: no tools unless you opt in.
• Sharing a list across sessions with CLAUDE_CODE_TASK_LIST_ID still needs the tools in each session.

When you want the plan outside the terminal

The built-in list is a good checklist for the session in front of you. It lives in ~/.claude/tasks/ on one machine and in one terminal. If you want to see the plan from a browser or your phone, across Claude Code and other agents, the agent has to report it somewhere shared.

Taskhold is built for that: Claude Code plans each task into steps with taskhold_plan and reports progress with taskhold_progress, and you watch it on a live board, on any model, alongside Codex or Cursor. Both can run at once: the built-in list for Claude's own short checklist, Taskhold for the tasks you queue and follow.

FAQ

Does turning the task tools back on cost anything?

The tool definitions and their reminders use some context on every turn, which is the reason they're off by default on newer models. Nothing else changes.

Is TodoWrite coming back?

TodoWrite is disabled by default in favor of the four Task tools. Where the task tools are available, setting CLAUDE_CODE_ENABLE_TASKS=0 gives you TodoWrite instead.

Which Claude Code version changed this?

The tools reference says the default set applies in Claude Code v2.1.268 and later. Run claude --version to check yours.

Sources

• Claude Code docs: task tool availability, checked 2026-10-26
• Claude Code docs: task list, checked 2026-10-26

Related

• Taskhold vs Claude Code's built-in task list
• See what your coding agent is doing right now
• Task list MCP server for Claude Code
• Taskhold vs Claude Code agent view

About Taskhold

Taskhold is a hosted task list shared by a person and their AI coding agents over MCP. Agents break tasks into steps and report progress, and the person watches a live board. $12/month or $120/year per person, 7-day trial with a card, no free plan. Made by Great Work LLC.

• Pricing: https://taskhold.com/pricing.md
• Agent index: https://taskhold.com/llms.txt

I make Taskhold, a task list shared by you and your coding agents. Originally published at taskhold.com.