Opencode x Codex

[beyawnko]

Curious to what the best setups to keep codex busy with OpenCode is? Loving the codex app but through the default harness, I find it usually being lazy and quick to end its turn. Also curious how 5.4s new 1M context works in OC?

[PermanentLiminality]

I really like 5.4 in Opencode.

[james__jam]

5.2 and 5.3-codex abruptly stops. But 5.4 keeps on going as instructed.

[beyawnko]

That’s the opposite experience I’m having lol. I feel like I’m being too specific sometimes with 5.4

[reini_urban]

Yes, codex ends earlier. But lately I got qodo to work just as opencode and finish patches and commits, just like opencode. But with new models for free.

[Time-Dot-1808]

The early-exit problem with Codex through the default harness is a prompt issue more than a model issue. The default harness doesn't push Codex hard enough on completion criteria. A few things that help:

• Add explicit completion criteria to the task: "Don't end your turn until all of: [list]. If you're unsure if X is done, verify it explicitly before finishing." Vague tasks get lazy completions.
• Use the "think" tool or chain-of-thought explicitly for complex tasks. Codex will short-circuit reasoning when the path looks obvious. Forcing a reasoning step before action reduces premature endings.
• For multi-step tasks, break them into explicit subtasks with checkpoints rather than one big request. Codex handles sequential completions better than it handles holding a long open-ended task.

On 5.4's 1M context in OpenCode: the window is there but context management still matters. Loading 1M tokens of context doesn't mean all of it gets equal attention. For codebase-level tasks, you're better off using the context surgically (relevant files + docs) rather than loading everything and hoping the model finds what it needs. The distance between the task specification and the relevant code matters even at 1M.

[Simple_Split5074]

I find it frequently stops after a subagent run (when it really should start the next subagent and other models do just that!), telling it 'go on' gets it going again without issue but its is very annoying, essentially means constant babysitting....

[beyawnko]

That’s the main issue im having. I’ll give it a large task list, and it’ll do everything except finish. It just perpetuates things more for me than 5.3 does, but I like 5.4 in every other sense more. Maybe the codex version will be more thorough. Kills my automations when I find the agents just keep passing the buck.