✨ Add Planning Mode support with /plan and /code commands#1
Conversation
Implements Planning Mode feature that allows users to switch between
planning-only mode and normal code execution mode via slash commands.
Changes:
- Add agent_mode reactive property to ConversationContainer ('plan' or 'code')
- Add /plan and /code slash commands to switch modes
- Add SetAgentMode message and handler in ConversationManager
- Add PLANNING_MODE_INSTRUCTIONS to guide agent behavior in plan mode
- Add blue mode indicator in WorkingStatusLine when in planning mode
- Add blue border color for InputField when in planning mode
- Update tests for new commands and add planning mode tests
In Planning Mode:
- Agent focuses on understanding requirements and asking questions
- Agent generates PLAN.md instead of executing code
- UI shows blue indicator and border to match GUI behavior
Closes OpenHands#613
Co-authored-by: openhands <openhands@all-hands.dev>
|
@ixchio |
I ran it locally via the SDK and pushed the branch manually |
|
I'm on it! ixchio can track my progress at all-hands.dev |
SummaryThe PR comment was a question from @maveilo asking how the PR was created automatically without mentioning @OpenHands on GitHub. Answer: The PR author (@ixchio) already provided the answer: "I ran it locally via the SDK and pushed the branch manually." This was simply a Q&A exchange about the development workflow - not a code change request. I verified:
No code changes were made because none were requested. The question has already been answered by the PR author. |
Hey! 👋
This adds Planning Mode to the CLI - now you can have the agent focus on planning before jumping into code.
The gist
Type
/plan→ agent plans instead of codingType
/code→ back to normalIn planning mode, the agent will ask questions, understand your requirements, and create a
PLAN.mdfile - no code execution until you're ready.Visual cues
When you're in planning mode:
Testing
All 1270 tests pass ✅
Closes OpenHands#613