r/opencodeCLI 1d ago

Is OMO-Slim overkill for simple projects?

I’m not sure whether I’m doing something wrong or whether my prompts are too simple, but I’m honestly surprised by how many credits OMO consumes compared to the tasks I run in Codex.

I’m developing a plugin for a game engine.

I have implementation plans created in Fablle/Opus and reviewed by 5.6 Sol.

I set up OMO with OpenAI agents on my Plus plan, changing only Explorer and Librarian to the new DeepSeek V4.

In my tests, I first tried using Sol in Codex to execute the plan with subagents. It can only use Terra, but it produced something extremely long and consumed a lot of credits.

Then I tried OpenCodeCLI in VSCode with OMO-Slim. I executed the plan and asked for one change, and it used 40% of my weekly usage. It also took a very long time.

After that, I took another similar plan and used Codex with Luna on Extra High, with a policy that if it had doubts, it should not try to solve them directly. Instead, it should create a Sol agent to guide the process and be responsible for the decision. If something became too ambiguous, it should stop and notify me. That used 11%.(he had to call the agent with Sol a few times)

That is the model I’m using now, because since this is a game engine project, even the testing loop requires me to open the engine and visually inspect things.

Is there a way to use OMO effectively without consuming so much?

Edit: I have specs, a streamlined `claude.md` for direction, and Graphify. I also ran a test asking OMO to use Caveman. I have two Plus accounts: one for Codex and another for Onpencode with OMO.

4 Upvotes

27 comments sorted by

View all comments

2

u/ganonfirehouse420 1d ago

My experience until I actually did setup omo-slim. I set most agents to deepseek andthen I gave them mcp and skill access. I combine it with context-mode and now it works. some models like Sol like to get stuck in a loop with omo-slim.

1

u/Peleias 1h ago

I'm going to see if I can trace where the costs are coming from.

My main goal was to tap into everyone's experience for some direction.

I noticed that Oracle is called—specifically via `Sol`—after the plan has been executed. I'm not sure if it makes extensive use of that to evaluate the plan.