Custom agent creation depending on the project

[aktasberkin]

Hi, great plugin you got here, thanks a lot for creating this.

I want to ask something though, do we have the ability to let omc create custom agents (teammates) depending on what the project is? Right now it produces the number of agents I input like worker-1, 2 ... But wouldn't it be better if omc decided what type of agents would it need depending on the project and set them up like that? Is this already a feature that I'm unaware of? If not, I will post this as an idea.

Thanks a lot for the great project!

[marky731]

I was wondering the same thing

[pluto2060]

The pattern that works here: classify the task type first, then route to specialized agents rather than generic worker-N instances.

A few categories that tend to need different agent profiles:

• code tasks → implementation + QA agents
• research tasks → explorer + synthesizer
• business tasks → researcher + content writer

The key is having a task classifier that reads the goal description and maps it to an agent configuration — not just "N workers" but "which specialist for this work".

The other piece that's missing from generic worker setups: the agents don't learn what worked per task type. If you persist which agent profiles succeeded on which task types, future runs can skip the trial-and-error phase.

We built this as the Skill Router in Entity (a self-evolving outer loop on top of Claude Code) — it classifies the goal, selects relevant skills from the installed pool, and tracks which ones actually improved the score. After a few runs, the routing gets project-specific automatically.

Code here if useful: https://github.com/jaytoone/HarnessOS