ccprogress

2026 年 10 月 15 日，Claude Desktop 官方已支持任务进度展示，CCProgress 完成了使命！

English · 简体中文

In a long session the spinner only tells you how long Claude has been working and how many tokens it spent. ccprogress adds the missing part: the plan, which step is running now, and how many are left, updated live as each step starts and finishes.

See it

From a real Desktop app session: step 3 of 6 is running, with the checklist unfolded.

In the Desktop app the bar lives in the band above the prompt for the whole turn. View steps unfolds the checklist in place, and a finished plan can be dismissed or simply clears when you send your next prompt.

From a real terminal session: step 4 of 6 has been running for 2 seconds, and its report is folded into one line.

In the terminal the bar sits right above the spinner, and each progress report folds into a single dim line such as ◦ 3/5 Run the tests instead of printing the whole step list into the transcript.

Install

Or, inside a session: /plugin marketplace add amigoer/ccprogress, then /plugin install ccprogress@ccprogress. Run /reload-plugins in sessions that were already open. A plugin installed at user scope loads in both the terminal and the Desktop app.

Then give Claude a task with a few steps. The bar appears as soon as Claude lays out its plan.

How it works

ccprogress is a mod: a plugin whose code runs inside Claude Code and can draw in its interface.

Where the steps come from. The bar needs someone to name the steps, so ccprogress uses the first source the session has:

1. The built-in TodoWrite tool, where the build offers it.
2. The built-in task list (TaskCreate / TaskUpdate), read back from the task files under ~/.claude/tasks/ after each update. Current builds turn these tools on with CLAUDE_CODE_ENABLE_TODO_TOOLS=1;…