claude-code - 💡(How to fix) Fix Plan mode: allow inline back-and-forth commenting on the plan (Google Docs style) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52049Fetched 2026-04-23 07:37:55
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Problem Plan mode already lets me attach inline comments to specific parts of the plan — great. What's missing is the back-and-forth: the agent can't reply to a comment in-thread, and I can't reply back to its reply. Every comment is effectively a one-shot note that only lands when I end my turn and the agent processes everything together. For non-trivial plans this is painful — I either approve plans I'd rather iterate on, or I burn turns re-explaining context in the main chat instead of the plan surface where the anchoring lives.

Proposal Turn each inline comment into a real thread, Google-Docs-style:

  • Agent can reply to my comment in-thread, anchored to the same selection.
  • I can reply back without ending my turn — ideally live / streaming as I type, so the agent can respond to a clarifying question the moment I hit submit instead of waiting for a full plan-mode turn cycle.
  • Threads are resolvable; resolved threads collapse; unresolved threads block ExitPlanMode until acknowledged.
  • Agent revisions to the plan file are linked to the thread that prompted them, so I can see why a step changed.

Why it matters Plan mode is the highest-leverage collaboration surface in Claude Code for anything non-trivial. Comments without threaded replies are a half-built version of this — the UI implies a conversation the backend doesn't support, which is more frustrating than no comments at all.

extent analysis

TL;DR

Implementing threaded comments with real-time updates and resolution tracking can enhance the collaboration experience in plan mode.

Guidance

  • To achieve the proposed functionality, consider modifying the existing comment system to support nested replies, allowing agents to respond to user comments in-thread.
  • Introduce a real-time update mechanism, enabling users to see agent responses as they are typed, and allowing for immediate feedback and iteration.
  • Develop a resolution tracking system, where threads can be marked as resolved, and unresolved threads block the ExitPlanMode until acknowledged.
  • Link agent revisions to the plan file to the corresponding thread, providing context for changes made.

Example

No code snippet is provided as the issue lacks specific technical details.

Notes

The proposed solution requires significant changes to the existing plan mode and comment system, and may involve updates to the backend, frontend, and database.

Recommendation

Apply workaround: Implement a basic threaded comment system with manual updates, allowing users to reply to comments and agents to respond in-thread, as a temporary solution until a more comprehensive real-time update mechanism can be developed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING