anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Feature: Seamless Plan-to-Build handoff with context retention #4138

New Issue
Open
opened 2026-02-16 17:42:45 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 17:42:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @lout33 on GitHub (Jan 3, 2026).

Originally assigned to: @thdxr on GitHub.

Problem

When using Plan mode to design an implementation, switching to Build mode requires:

  1. Pressing Tab to switch agents
  2. Re-explaining what to build (e.g., "go ahead and implement it")

This creates friction and redundancy since the plan context is already established.

Proposed Solution

After completing a plan, the Plan agent should:

  1. Suggest switching to Build mode (e.g., "Ready to build? Press Tab to switch and I'll start implementing.")
  2. When user presses Tab, Build agent should automatically continue with the plan without requiring the user to re-prompt

Essentially: Plan agent hands off context to Build agent seamlessly.

Expected Behavior

User (Plan mode): "Plan how to add dark mode toggle"
Agent: [Creates detailed plan]
Agent: "Plan complete. Press Tab to switch to Build mode and start implementing."
User: [Presses Tab]
Agent (Build mode): [Immediately starts implementing based on the plan - no re-prompting needed]

Current Behavior

User (Plan mode): "Plan how to add dark mode toggle"  
Agent: [Creates detailed plan]
User: [Presses Tab]
Agent (Build mode): [Waits for user input]
User: "Go ahead and implement the plan" <-- redundant step

Additional Context

This would make the Plan/Build workflow much more fluid, especially for complex multi-step implementations where the plan context is critical.

Originally created by @lout33 on GitHub (Jan 3, 2026). Originally assigned to: @thdxr on GitHub. ## Problem When using Plan mode to design an implementation, switching to Build mode requires: 1. Pressing Tab to switch agents 2. Re-explaining what to build (e.g., "go ahead and implement it") This creates friction and redundancy since the plan context is already established. ## Proposed Solution After completing a plan, the Plan agent should: 1. Suggest switching to Build mode (e.g., "Ready to build? Press Tab to switch and I'll start implementing.") 2. When user presses Tab, Build agent should **automatically continue with the plan** without requiring the user to re-prompt Essentially: Plan agent hands off context to Build agent seamlessly. ## Expected Behavior ``` User (Plan mode): "Plan how to add dark mode toggle" Agent: [Creates detailed plan] Agent: "Plan complete. Press Tab to switch to Build mode and start implementing." User: [Presses Tab] Agent (Build mode): [Immediately starts implementing based on the plan - no re-prompting needed] ``` ## Current Behavior ``` User (Plan mode): "Plan how to add dark mode toggle" Agent: [Creates detailed plan] User: [Presses Tab] Agent (Build mode): [Waits for user input] User: "Go ahead and implement the plan" <-- redundant step ``` ## Additional Context This would make the Plan/Build workflow much more fluid, especially for complex multi-step implementations where the plan context is critical.
yindo commented 2026-02-16 17:42:45 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 3, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #4536: [FEATURE]: QOL improvement of plan -> build

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 3, 2026): This issue might be a duplicate of existing issues. Please check: - #4536: [FEATURE]: QOL improvement of plan -> build Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:42:46 -05:00
Author
Owner
Copy Link
Copy Source

@justfortheloveof commented on GitHub (Jan 3, 2026):

Hey @lout33, you could create a new primary agent to achieve this, without changing the behavior of the default agents for the rest of us.

@justfortheloveof commented on GitHub (Jan 3, 2026): Hey @lout33, you could create a new primary agent to achieve this, without changing the behavior of the default agents for the rest of us.
yindo commented 2026-02-16 17:42:46 -05:00
Author
Owner
Copy Link
Copy Source

@airtonix commented on GitHub (Jan 3, 2026):

this can just be a plugin tbh

@airtonix commented on GitHub (Jan 3, 2026): this can just be a plugin tbh
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4138
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?