Hand a task to another agent.
You are working with one agent and want a second one to take a self-contained job in another project, so you can carry on with your own work.
The conversations on this page are illustrative: they show the shape of the calls and answers, not captured output.
With the default restricted-tool request, give the session a registry containing what the job needs and check support for the installed provider release. See Safety and limits.
Follow a long task and stop it.
A task runs for minutes. You want to see what the helper is doing, and stop it if it wanders off.
Sending a second message while a turn is running is refused. Interrupting a turn to send new text is not offered by any helper program, so stop the turn first, then send.
Come back to a conversation later.
You closed a session yesterday and want to carry on where it stopped, or try a different approach from the same point.
Detach a session on close only deliberately, when you will recover it from another connection (see the tools reference); it can leave the turn running. Reclaimability after an ordinary disconnect is not immediate. Follow resume, reclaim and fork for ownership, explicit execution mode, retained settings and cleanup.
Keep a helper to the tools you chose.
You want a helper that can read documentation and use a browser but cannot run commands or change your files.
Accepting a helper program release the setting was not checked on is possible, but it may then fail to remove every built-in tool. Choosing to keep built-in tools gives the provider broader access within its selected execution environment. Both options are described in Safety and limits.
Run several sessions side by side.
You have two independent jobs, each in its own project folder, and you want them to run at the same time.
Review each result, then close sessions you no longer need; preserve important results before purging. Opening is limited to 10 sessions a minute and sending to 30 messages a minute across all clients of the server. When the session limit is reached, the agent is told to close one first.
Things mcp-aic does not do.
It does not ask you to approve each action a session takes: your controls are the folder, the registered tools and native_tools. It does not return tool output. It does not start the registry for you, and the nested mode needs an image you prepare.