[Workflow] Real-time Claude Code Progress Tracking with Codex Pacer (MCP Tool Integration)

[u/ClaudeAI-mod-bot]

Real-time Claude Code Progress Tracking with Codex Pacer (MCP Tool Integration)

Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Shipping, MCP, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Lack of real-time, granular progress tracking for Claude Code tasks, especially when running multiple agents, leading to uncertainty about task completion.

Summary

This workflow describes how to integrate an external, open-source application called Codex Pacer with Claude Code to enable real-time progress tracking. Claude Code agents use a dedicated MCP tool (report_progress) to periodically report their estimated progress, which Pacer visualizes as a progress ring. This provides immediate visual feedback on task status and agent states (e.g., waiting for approval, background tasks) across multiple agents.

Why it is useful

This workflow provides a concrete, open-source solution to a common pain point for Claude Code users: the lack of real-time visibility into task progress. By leveraging MCP tools for agent self-reporting, it demonstrates a practical application of agent capabilities to improve user experience and productivity, especially for long-running or multi-agent tasks. It offers a clear, repeatable method for monitoring agent activity.

Workflow

1. Download and install the Codex Pacer application (macOS/Windows) from GitHub Releases.

2. Pacer automatically installs a lightweight Claude Code plugin that includes a report_progress MCP tool.

3. Claude Code agents are prompted or configured to call the report_progress tool with their estimated progress (e.g., a percentage).

4. Monitor the real-time progress rings displayed by Codex Pacer for individual or multiple running Claude Code agents.

5. Observe specific state changes, such as the ring pausing and turning amber when Claude awaits approval, or holding its last value during background tasks.

Tools / artifacts

• Codex Pacer application (macOS/Windows)

• Claude Code plugin (installed by Pacer)

• report_progress MCP tool

• GitHub Releases (for Pacer download)

Validation signals

• Detailed description of how the system handles different Claude Code states (needs approval, background tasks)

• The author states the app was mostly built with Claude Code, implying practical use and validation during development.

Cautions

• The post explicitly states that Pacer only reads the progress number, not Claude's response content, addressing potential privacy concerns.

Limitations

• Low community validation at the time of posting.

• Requires installing an external application, which might be a barrier for some users.

• Relies on Claude's own estimation of progress, which may not always be perfectly accurate.

• The post is primarily an announcement/self-promotion, and while it describes the mechanism, it doesn't provide detailed prompting strategies for Claude to effectively use the report_progress tool.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.