Allow inline annotations on plans
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Problem
When reviewing a generated plan, requesting changes requires restating the step and surrounding context in chat. This is verbose and error-prone.
Proposal
Allow users to select plan text or a plan step and attach an inline annotation. When submitted, annotations should be sent to the agent anchored to the exact plan location.
Desired UX
- Add comments directly to a line, selection, or step.
- Collect multiple annotations before requesting a revision.
- Preserve annotations across plan revisions, marking anchors stale when needed.
- Show which annotations were addressed and which remain unresolved.
Benefit
This would make plan iteration faster and more precise, without requiring users to retype context.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the generated plan review flow and how revision requests are sent to the agent. Map the entry points for selecting plan text or steps, submitting multiple annotations, and rendering revised plans. Done means annotations can be anchored, preserved or marked stale across revisions, and shown as addressed or unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100