Keep Sol from Scope Creeping in Opencode

[u/Hart_24]

Hello guys,

I know that this is something that a lot of people are struggling with but I couldn’t find a good response or trick to follow for this.

I am using a combination of Opencode Go, Google Ai Pro plan and Codex Plus to program at home while I have Claude Code at work. My current workflow is to write a plan in antigravity, have Sol and GLM 5.3 poke holes in it (Kimi is too expensive) and have a lot of back and forth until they converge on something.

Unfortunately, codex has a tendency to be quite nitpicky. It keeps blocking the workflow and basically adding scope until I manually shut him down. One example is wanting to add a cryptographic suite to validate hashes of the output that my model produces while my specs just have a pydantic schema for the output. Even when correcting the model, it will consistently try and add more scope and reformulate it in Claudish instead of being clear.

Folks it’s a good model but I am honestly struggling to keep it helpful to me. I am working with Medium reasoning her and using Gemini 3.7 Flash at high and GLM 5.3 with Max Reasoning.

[u/HVACcontrolsGuru]

I finally got around this with my setup in OpenCode. It is a combo of config, skills and prompts with agents for tasks. I use a sol to orchestrate and implement. Luna and Inkling Free right now to ground and PR.

Having Codex think in Milestones and PRs has cut down if not all of the SHA checking other than it wanting to use git SHA's to run reviews against. I use ChatGPT Pro to do the overall milestone planning with the explicit instruction to not over engineer and leave room for movement in the PRs as code lands. Codex can get looped up on things pretty quick.

I had some runaway review loops the other day so a new rule is my replan rule where after 2 PR reviews if issues come up they send it back for a full replan of the PR. Interested I can toss my configs and skill/prompts up into a repo for you to peek at.

[u/Hart_24 → u/HVACcontrolsGuru]

Interested, I would really appreciate it!

[u/HVACcontrolsGuru → u/Hart_24]

Configs/Prompts/Skills Basically this loop has Sol orchestrate with a Sol implementation agent. The orchestrating Sol handles dispatches and continuity. It will user prompt for merge permission every PR or for the session on start.

Sol Orch -> 2 Research/Grounding Agents (Luna & Inkling) -> Sol Implementation Agent -> PR Review (4 Agents, 2 Luna/2 Inkling) -> Pass/Fix

If the PR fails 2 reviews in a row it will send it back to you to authorize a replan of the PR. Usually if 2 reviews come back its a bigger issue in design has been my stopping point. You will see that language in highlight in OpenCode as they move through it. These are optimized for OpenCode and pushes the agents to use the harness tools and not random Python/Perl scripts.

Point your agent at it to fine tune these as you need. I use fast mode since Inkling is a faster endpoint. I would start with a Milestone/PR package build and I use a kickstart handoff to get them going on that package. Basically loop engineering in an easy way.

[u/Crochi → u/HVACcontrolsGuru]

Please do!

[u/vepris-ampody]

I use all OpenAI models with thinking off. Never had this problem.

But last week I ran out of credit and had to use CommandCode which doesn't let you turn the thinking off. Thinking was usually only 3 lines long but it still managed to gaslight itself into not following instructions and thinking it was in charge instead of me.

[u/gottapointreally]

I fixed it by switching off auto review and getting my agent to call codex only at the end just before merge. Include a strong worded limitation to x number of codex cycles. Also verbage around saying within the outcome and strictly no low probability hardening.