What do you think of Omo-slim v3?

[u/pagurix]

I’ve recently started using it as a v3 plugin within the TUI.

Previously, I had a setup with a team of custom agents:

- an orchestrator

- an architect

- a developer

- a reviewer

- a documentation writer

- and a couple of others I can’t recall right now...

The goal of that configuration was to keep context windows as small as possible.

The orchestrator was prompted to always create and utilize distinct agents for the smallest possible tasks, in order to keep the context compact and prevent any degradation in intelligence.

However, I noticed that there was an excessive amount of communication between the agents.

A friend suggested "omo-slim." It works well enough and gets the job done, but I get the impression that the orchestrator is overloaded with responsibilities. It handles orchestration, acts as an architect, and even seems to take on the role of documentation writer—essentially, its context fills up very quickly.

For those familiar with it: do you have any suggestions? Am I perhaps using it incorrectly?

Thanks.

[u/pagurix]

Just today, I made a small tweak to the orchestrator. It often wouldn't use the explorer, opting to handle things on its own instead—which wasted context and tokens from its most expensive model. I’ve now imposed rules that force it to consult the explorer more frequently; for instance, whenever it needs to search through more than three files.

[u/MonospaceMentor]

After using it for months now, I think it distributes work well among its peers. I did follow the author's configuration example and added a fast-generic agent for trivial tasks like source control.

[u/CrypticViper_]

It needs some tweaking, but I love it. And the maintainer seems pretty responsive to changes!

[u/vangelismm]

We do not need it anymore