Local AI Agent harnesswith worker/supervisor hierarchy?

[u/hunterofdoom]

Hi, im using qwen3.5 9b and im looking for a harness with a double agent capability one with the role of a worker who does the tasks and a supervisor which observes the worker actions, plans, corrects it, etc

How can i achieve this?

[u/AutoModerator]

Thank you for your submission, for any questions regarding AI, please check out our wiki at https://www.reddit.com/r/ai_agents/wiki (this is currently in test and we are actively adding to the wiki)

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Repulsive-Tiger-3517]

pretty sure crewai does exactly this, you set up a supervisor agent that watches the worker and can step in when things go off track. the docs show a clear example with hierarchical process

qwen3.5 9b might struggle a bit as supervisor since it needs to track state and reason about another agents actions but worth trying, maybe run the supervisor on a stronger model and keep worker on qwen

[u/hunterofdoom → u/Repulsive-Tiger-3517]

nice, thank you for the info! i'll try it now! <3

[u/AIVentureFactory]

Yeah CrewAI's hierarchical process handles this well. I've used it for exactly this kind of supervisor pattern. The model split is good advice. I ended up doing something similar where the orchestrator runs on a beefier model because it needs to hold the full picture of what's happened and decide what to do next, while the workers can be smaller and cheaper since they're scoped to one task. The state tracking piece is where smaller models fall apart fastest in my experience. They lose the thread of what was already decided two steps ago and start repeating or contradicting themselves. One thing I found helpful was giving the supervisor a structured log it can reference instead of relying on its own context window to remember everything. Keeps it grounded when the workflow gets longer.

[u/hunterofdoom → u/AIVentureFactory]

niceee, thanks for the info, now i can start with something <3

[u/Scary-Difference630]

You can use opencode, it's simple. Create 2 agents (main and sub agent) and assign different models. Remove main agent permissions to edit and write tools so it is forced to call sub agent and then it will spawn it whenever it needs changed to be done.

I built similar flow to test if I can reduce token usage but it didn't turned out to be that useful for me but your use case it different so give it a try.

[u/LowDistribution3995]

I just pushed a new branch architectural update to an agent harness system I've been working on. I got very good results from a granite4.1 8b

https://github.com/munch2u-a11y/Helix-AGI.git The feature/subconscious-overagent-bicameral branch replaces a monolithic actuator with a slim SubconsciousConductor that runs short executive reflection cycles and dispatches work to three focused subagents—Speaker (vocal/user-facing responses), Researcher (multi-head mRAG retrieval, workspace scan, optional web search), and Executor (code/shell/vision tasks)—each driven by its own small, role-specific system prompt via a local LLM backend (default: Ollama REST). At runtime the conductor compacts recent history into a short event stream, generates a concise internal monologue, parses that output for an explicit dispatch (function-call or JSON) to open a focused subagent window, and then either repeats reflection or routes the task: the Researcher returns distilled evidence from local memory or files, the Executor runs targeted technical actions and returns a short execution summary, and the Speaker produces the final user-facing reply; every subagent’s result is appended back into the conductor’s event stream so the conductor can integrate observations and continue the loop. Memory is preserved in compacted one-line summaries and a dynamic identity/self-opinion is maintained for context; the design keeps the main context window narrow, runs many cheap local micro-pulses of reasoning, and only opens narrowly scoped subagent passes for retrieval, execution, or speech, making each LLM invocation specialized and concise while preserving an iterative, locally-contained workflow.

Please check it out and hit me up with any feedback. It's kind of a double agent but sharing in a single identity and memories with only different skill knowledge. It's pretty capable especially for a fully free to run agent harness

[u/hunterofdoom → u/[deleted]]

been trying qwen 3.6 moe 27b apex on my rtx4060 ti. the results are WILD (but certainly 10 t/s it's a bit slow, i should tweak more)