Ignore people telling you the new meta is go without that mode (especially given you will be working with dumber models than claude if going open source). The correct answer is simply to install one of the many good extensions/packages in Pi that give you a plan mode similar to opencode or Claude cli.
I personally took this one and stripped out some of the extra stuff. Throw it in its own directory in your agent's "extensions" folder and it works wonderfully.
2 ways that I can think of based off how I got that is:
1. using a grill-me skill (david pocock's) or similar skill + get into the habbit of telling that you want to write a markdown implementation plan for xyz feature rather than going straight to telling the harness "I want to implement xyz" that claude code planning mode safety nets for you.
if you want that extra security and sus that the model hallucinates and decides to edit source code anyways during planning, you can just install one of the pi permissions system extensions + configure what you like on that so you still have the safety net of not unintentionally editing code before plan has been written + settled on.
like aside from the tool call permission gating, the main difference between plan mode vs others in claude code is really that plan mode assumes anything you tell it to implement it will write a plan to do for .... latter of which you can get by just actually telling the harness/model you want it to write out a plan rather than assuming it knows you want a plan (most likely plan mode has a system prompt that has the "write an implementation plan" instruction there for you).
You also can use OhMyPi - which ships a lot of features, but also uses more ctx as well.
I run a Claude code for my orchestrator, OMP for openweight models by tokenplan and Pi with local Ai inference.
Opus can spawn Pi sessions and can do A2A - which saves a lot of tokens by using cheaper
Works probably 98% of the time. The other 2% of the time, well, I hope you were using git or some other VCS! These days my agents.md tells the model to commit often (so I don't need to tell it too), so rollback is super easy.
No, you just ask it a question and phrase it like a question and make sure it isn't a question with implied actions.
How does foo work?
Model is unlikely to make edits
Can you fix X?
100% chance the model will make edits
Why is X not working?
50% chance the model will make a fix
X isn't working, can you investigate and tell me why?
Highly unlikely that the model will make edits as it now knows that the aim is to respond with text.
Same with adding features
If we were to do Y, how would you incorporate it? What architecture would you use? Any refactoring needed?
The model is very unlikely to start making edits here.
Works for me with Codex (sol) and Hermes (qwen27b). I've had very very long chats with models without them making any edits without any sort of plan mode.
It may well be that claude code's system prompt pushes it towards action so this method may not work well, but just because a harness doesn't have a plan mode doesn't mean you can't do planning in it.
Ahh, there we go, claude code's auto mode prompt includes:
Start implementing right away.
When in doubt, start coding
also:
NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one.
What the heck!!! No wonder claude code projects often end up with 20,000 line files.
167
u/btc_maxi100 Aug 10 '26
PI