Delegation
How your agents hand work to each other. Ask the wrong agent and the right one picks it up in its own conversation — with a notification the moment it starts.
You don't have to remember which of your ten agents owns which job. Ask Ashley to draft an email and she won't fumble it — she hands it to Maya, who opens her own conversation and does the work properly, with the real inbox tools.
That's delegation. It isn't a personality trick in a prompt. Each agent has a hard-enforced toolbox at the runtime level: Ashley literally cannot reach your inbox, because the email tools are not mounted for her. Delegation is what turns that boundary from a dead end into a hand-off.
Why the boundary exists
Only Maya has your Gmail or Outlook. That's enforced twice — once at the prompt layer, once at the runtime layer where the email tools simply aren't in Ashley's tool list. A limit you can rely on is worth more than a promise you can't check. Delegation is how the limit stays convenient.
Two ways work moves between agents
Unyo has two distinct mechanisms, and they feel different in use.
| Hand-off (now) | Assigned task (later) | |
|---|---|---|
| What triggers it | An agent hits something outside its toolbox | You (or an agent) explicitly assign a mission |
| What happens | The coworker opens its own conversation and starts working immediately | A real task lands in your Neural Core, assigned to that agent |
| You get | A red badge on the coworker's avatar the moment it starts | The task in your sidebar list, with the agent's badge on it in the Tasks modal |
| When it runs | Straight away, in the background | The next time you open a conversation with that agent — it proactively offers to do it |
Both are real records, not narration. A hand-off creates an actual conversation you can open and read. An assigned task creates an actual row in your task list you can see, edit or tick off.
What a hand-off looks like
- You ask Ashley: "can you email this week's post recap to my co-founder?"
- Ashley recognises she has no inbox tools and hands the mission to Maya.
- Maya opens a new conversation of her own and runs the full pipeline there — her tools, her context, your Neural Core, your credits.
- A red badge appears on Maya's avatar right away, on the home grid and in the sidebar, with a chime. You don't wait for her to finish to know it happened.
- Ashley tells you Maya is on it, and carries on with what she can do.
- You open Maya's conversation to read the work and approve anything that needs sending.
The first agent doesn't get the answer back
A hand-off is a hand-off, not a sub-task. Ashley never sees what Maya produced — she passes the mission and moves on. The result lives in Maya's conversation, which is exactly where you'd look for it anyway. Don't expect the two agents to merge their work into one reply.
How to hand work off deliberately
You don't have to wait for an agent to notice. Just say it.
Or assign it as a task in your Neural Core, to be picked up in that agent's next session:
The assigned task appears in your Tasks list in the sidebar. Open the Tasks modal to see which agent it's assigned to — the task carries that agent's coloured badge. When you next open a conversation with Blake, he sees it flagged as assigned to him and offers to run it.
Who can be delegated to
Nine agents can receive work: Ashley, Maya, Alex, Riley, Tyron, Sam, Lucy, Blake and Ema.
Steve cannot be delegated to
Steve, the website agent, is not a delegation target. No agent can hand him a site to build, and you can't assign him a task from another conversation. If you want a website, open a conversation with Steve yourself — that's the only route in. Steve can hand work out to the other nine; nobody can hand work in to him.
Guardrails
- Depth-1. A conversation that was itself created by a delegation cannot delegate again. Maya, working on a mission Ashley handed her, can't bounce it to Lucy. Two agents deep is where it stops — no runaway chains of agents handing work to each other while you watch your credits drain.
- Capability-accurate. An agent is only told to delegate something it genuinely can't do. The system reads the agent's live tool list at run time and works out what's actually missing, so a specialist is never told to delegate a job it's holding the tools for.
- Your account, your rules. The coworker runs on your own session — same credit balance, same connected accounts, same Neural Core. It's not a separate service with separate access.
- Nothing gets sent. Delegation moves work, not permission. A delegated Maya still drafts and waits for you. Nothing is sent, posted or published without you saying so.
Why the coworker starts fresh instead of joining the chat
Because it's your record, not a performance. The coworker's conversation is a real, titled, permanent thread with its own steps, its own drafts and its own artifacts. You can reopen it next week and read exactly what happened. If the hand-off happened invisibly inside the first agent's reply, you'd have a paragraph claiming work was done — and no way to check.
The Neural Core is what makes this work without repetition. Every agent reads the same memory — your brand, your products, your contacts, your preferences — so the coworker starts the mission already knowing what you'd otherwise have to re-explain. Tell Maya you hate emojis and Ashley knows on her next run. See the Neural Core.
Tips
- Don't route by hand. You'll be right less often than the system is. Ask whoever you're already talking to and let it move.
- Follow the badge. The red count on an agent's avatar is where the finished work is. Open that conversation, not the one you asked in.
- Be specific in the mission. The coworker gets your instruction, not your whole conversation. "Email the recap" travels worse than "email Théo the recap of this week's posts, casual tone, before Friday."
- For a website, go to Steve directly. Every time.
Do the agents talk to each other?
Not in the chat-together sense. One agent passes a mission to another, and the second one does the work in its own conversation. There's no back-and-forth between them, and the first agent never receives the result — you do, in the coworker's conversation.
How do I know something was delegated?
Two ways at once. The agent tells you in the reply, and a red badge with an unread count appears on the coworker's avatar — on the home grid and in the sidebar — the moment the hand-off happens, with a chime. The badge clears when you open the conversation.
Can I ask any agent to build me a website?
No. Steve is the only agent who builds websites, and he's the one agent you can't delegate to — no agent can hand him a job. Open a conversation with Steve yourself and describe the site.
Can a delegated agent delegate again?
No. Delegation is capped at one level. If a conversation was created by a hand-off, that agent can't hand the work on again — it either does the job or tells you what it can't do. This is deliberate: it makes runaway agent-to-agent loops impossible rather than unlikely.
Does a delegated agent send emails or publish posts on its own?
No. Delegation moves the work, never the authority. The coworker prepares the draft — the email, the post, the document — and it waits for you. There is no unattended send or publish anywhere in Unyo.
Which agents can receive delegated work?
Nine: Ashley, Maya, Alex, Riley, Tyron, Sam, Lucy, Blake and Ema. Steve is not on the list.
Troubleshooting
The agent said it would delegate but no badge appeared. Check the coworker's conversation directly from the sidebar — the badge only shows unread items, and if you already had that conversation open, it may have cleared instantly. If there's no new conversation at all, ask the agent again and name the coworker explicitly.
An agent refused to delegate and did the work itself. That's usually correct: the system checks the agent's real tool list and only routes work it genuinely can't do. If the result is wrong for the job, name the specialist yourself — "give this to Blake".
"Unknown coworker" when you ask for Steve. Expected. Steve isn't a delegation target. Open a Steve conversation from the agent list instead.
You assigned a task to an agent and nothing happened. An assigned task waits for that agent's next session — it's a mission on their list, not a scheduled run. Open a conversation with them and they'll offer to take it.