Capability · Parallel
It runs a team, not one task at a time
It delegates a job to a team of sub-agents that run at the same time — and you can watch, steer, and stop them.
Real operators do not do everything themselves in sequence. Neither does monopea. When a job has independent parts, it delegates them to a team of sub-agents that run at the same time, then wakes to pull the results together — so a morning of work finishes in the time the slowest piece takes, not the sum of all of them.
This is what turns an assistant that does one thing at a time into something that operates like a team you direct. You set the objective; it fans the work out, keeps each strand moving, and reports back when the pieces are done.
Delegates work and runs it in parallel
Give it a job with several independent parts — research three markets, draft five outreach angles, clean up a pipeline while it writes the weekly update — and it spins up a sub-agent for each, running them side by side. Each strand carries its own context, so they do not step on each other.
When the sub-agents finish, the brain wakes on its own, integrates what they produced, and decides the next step — including delegating a fresh round if the work calls for it. You are not babysitting a queue; you are directing an operation.
- Independent work runs at the same time, not one after another
- Each sub-agent works in its own isolated context
- The brain wakes when the work lands and picks up from there
You can steer it mid-run — and stop it instantly
Work in progress is not a black box you have to wait out. Send a message while it is running and that instruction folds into the work in flight — add a constraint, change priorities, correct a wrong turn — without starting over.
And if you want it to stop, it stops. Halt any agent and everything it set in motion stops with it, immediately. Nothing keeps running behind your back.
- Redirect work in progress with a message — no restart
- Stop any agent, and everything it spawned, on command
- You stay in control while the work is live, not just before and after
Traceable and durable
Every sub-agent records what it did — the steps it took, the tools it called, what it produced — so you can look back at exactly how any piece of work happened, not just the outcome.
And the work is durable. If a sub-agent is interrupted, what it had already done is preserved, and the brain can read that progress, judge it, and carry on — instead of losing the effort and starting from scratch.
- A full record of what each sub-agent did, step by step
- Interrupted work is preserved, not lost
- The brain resumes from where things stopped, not from zero
Why it matters
Work finishes sooner
Independent tasks run together, so a big job takes the time of its slowest part — not the sum of every part.
Direct it like a team
Fan out the work, steer it while it runs, and stop it when you want. You are in the loop the whole time.
Nothing gets lost
Every sub-agent’s work is recorded and durable, so you can see what happened and interrupted work is never thrown away.
FAQ
Parallel operation, in short
- Does it really run tasks at the same time?
- Yes. When a job has independent parts, the brain delegates each to its own sub-agent and runs them in parallel, then wakes to integrate the results.
- Can I change direction while it is working?
- Yes. A message sent mid-run folds into the work already in flight, so you can add a constraint or correct course without starting over.
- Can I stop it?
- At any time. Stopping an agent also stops everything it spawned, immediately — and whatever was already done is preserved for you to review.
- What happens if something fails partway?
- The work done so far is saved. The brain can read that partial progress, decide what to do with it, and continue — rather than losing the effort.
Keep exploring