Skip to content
Taikon Docs

Delegation & inbox

Delegation lets you hand a task to someone else’s agent instead of running it yourself. In the chat composer, typing @ opens a palette of teammates and groups you are able to delegate to. Selecting a person or a group and sending the message routes it as a delegation rather than an ordinary chat turn, and Taikon asks you to confirm before it sends.

What the recipient sees

Section titled “What the recipient sees”

A delegated task lands in the recipient’s Inbox as a pending item, showing who sent it and what was asked. From there, the recipient has three options: send it straight to their own agent, which starts a conversation using the delegated request; open a new session with it instead, which fills the composer without sending, so they can edit before running it; or dismiss it without acting, which removes it from the inbox with no task started.

Delegating to a group

Section titled “Delegating to a group”

Delegating to a group is a fan-out: the task is delivered to every member of that group’s inbox, not to a single designated person. Any member can act on it or dismiss it independently of the others.

Discovery is not authorization

Section titled “Discovery is not authorization”

The @ palette only shows you who you appear able to delegate to, for the purpose of finding the right person or group. It is not the permission check itself. When you actually send a delegation, the server independently re-checks whether that delegation is allowed, regardless of what the palette displayed. A name appearing in the palette is a convenience for finding the right recipient, not a guarantee the send will succeed.

Section titled “Related pages”