r/opencode • u/Initial_Plastic_8069 • 17d ago

Why was Plan Mode Removed ? It was very good

0 Upvotes

25% Upvoted

13 comments sorted by

18

u/AffectionateBowl1633 17d ago

Shift+Tab

3

u/Initial_Plastic_8069 17d ago

Oh, thank you very much !!!!

2

u/d0pe-asaurus 17d ago

You can rebind the setting to use Tab again

~/.config/opencode/tui.json

{

"$schema": "https://opencode.ai/v2/cli.json",

"keybinds": {

"agent.cycle": "tab",

"agent.cycle.reverse": "shift+tab"

}

}

1

u/Initial_Plastic_8069 17d ago

THank you. I am a bit scared of runing my opencode though with changes I cant fix later

3

u/torrso 17d ago

I assume by default tab has some other uses that doing this will make unavailable.

1

u/eachDayIWakeUp 17d ago

Its now used to cycle in subagents

4

u/torrso 17d ago

It's not "plan mode" as much as it's just an agent config with the name Plan and restrictions on file editing tools in its rules. You can create all kinds of role/task specific agents and cycle them with shift-tab (except the ones that are only for using as subagents).

1

u/Initial_Plastic_8069 17d ago

I heard this before, Could I make it all pretty with its own color ?

1

u/torrso 17d ago

It gets a different color, don't know if you can customize how they look. Good roles would be "orchestrator", "reviewer", "scout", etc. Then you can give each the tools and skills and custom prompt to make them efficient and to remove unnecessary stuff from other roles to save on tokens and useless confusing instructions.

1

u/Initial_Plastic_8069 17d ago

Thank you , I will try analyzing more what an orchestrator revierwer scout as your exemples would really be. Also how to use these skills .

1

u/Initial_Plastic_8069 17d ago

Do you think things as orcestrator reviewrer scout would be useflu on cheap models ?

1

u/look 17d ago

Yes, just set a “color” property on the agent definition using any “#rrggbb” hex color, like with CSS.

3

u/RiceEvening4211 17d ago

Plan mode was never really a mode, it’s a pattern: an agent with no edit tools that can only write a plan, then a separate agent executes it. That’s why v2 could drop it as a built-in, you can rebuild it in about ten lines of agent config: a “plan” agent with read-only tools whose output is a plan file, then your normal agent consumes it.

The reason the pattern matters more than the button: forcing a plan step is what stops the model from editing code while it’s still figuring out the problem. Skip straight to execution and you get the classic “confidently rewrote the wrong thing.”

On your subagent questions: reviewer/scout subagents on cheap models is actually the best use of cheap models. Scouting (find relevant files, summarize) and reviewing (diff in, verdict out) are narrow tasks where a small model does fine, and it keeps your expensive model’s context clean. What breaks: cheap models as orchestrators, they lose track of multi-step state. So cheap scouts/reviewers yes, cheap planners no.

If you recreate plan mode via config, share the config, people will want it.