better plan mode
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 22/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- ai, design, developer-experience
Research direction
The issue names no files, tests, or entry points. Start by locating the existing plan-mode and agent-planning experience, then clarify the conversation flow, plan-building action, preview, and inline-comment requirements with the maintainer. Done would require an agreed scope and an implemented, testable planning workflow.
Written by the indexing model from the issue text.
Description
plan mode sucks, for a number of reasons:
- it's hard to give feedback on large plans
- there's no guarantee the agent will ask the right questions
- agent is very eager to just create the plan vs. having a conversation first
i wonder if we can roll our own "plan mode" that isn't just the agent's default, but some hybrid...
- conversation about the idea to flesh it out, make some decisions
- explicit "build plan" action that uses the plan agent to synthesize the convo into a plan
- better plan preview
- inline comments on the plan for iteration
i think this would be good day-to-day, but also sets up a really good UX for a use-case that i think is really neat:
- get a signal report, or come with your own idea
- plan with the agent in a non-claude-code-like-UI
- the plan gets passed to a bg cloud agent, instead of just the signal report
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
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.
More from PostHog/posthog
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
MotherDuck incremental sync never checks for duplicate primary keys, so the guard is a dead branch Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100