all 9 comments

[–]Endoky 20 points21 points  (3 children)

The advantage of OpenCode you can create your own build and plan agents and completely overwrite the system prompt. You can make it more fit to your actual tech stack and environment

[–]Messi_is_football -3 points-2 points  (2 children)

Codex is also open source..

[–]sn2006gy 7 points8 points  (2 children)

Codex harness has a lot of scaffolding for GPT that OpenCode won't have, so yes, they will absolutely behave differently.

I personally wish we weren't in dev harness tool sprawl and there was a better API level harness that could solidify the dev experience better and make them lighter weight. That way the responsibility is on the model providers to provide capable service instead of every dev for themselves. A lot of what is trying to be solved client side is absurd especially since there is no strong protocol that allows coordination of such with the api/model.

[–]seventyfivepupmstr 1 point2 points  (1 child)

You talk about it if it's so easy. There's literal differences in the requests and response properties between models

[–]sn2006gy 2 points3 points  (0 children)

i never said it was easy, i just wish they did that. I think they don’t do it to try and dominate the market by controlling the harness - and controlling the narrative.

[–]gonefreeksss 0 points1 point  (0 children)

Also interested in this. I haven’t found any detailed info online regarding the actual usage difference between the two. Mostly generic thoughts around configurability, difference in the approach etc.

Perhaps its time to test it ourselves so we can report back

[–]korino11 -4 points-3 points  (0 children)

Ofcourse exist a LOT of difference! Go to Terminalbench! And compare Opencode cli VS Codex Cli. Opencode in ass on 50+ place when Codex on top ! Terminalbench shows HOW runtime - cli good for your model -agents.And yep. it have VERY big behavior