Sending a Live Session to an AI agent

Use Send to AI agent during or after a Live Session to hand the meeting to an agent, folder, custom command, Chief task, or another chat app. You choose which session context to include and what the agent should do with it.

​

Ask an agent during a Live Session

You can also address Chief or a command-line agent while the session is still running. This starts a conversation about the live session; it does not create the session handoff described below. To ask Chief or one of your own agents:

1. Click Chat in the floating session control.
2. Click the @Chief addressee chip, or type @ at the start of the message.
3. Choose Chief or an available command-line agent. The menu also shows agents that are not installed and Where agents run when setup is needed.
4. Enter your request and send it. A local command-line agent starts on your computer and answers in a new chat. If the selected agent supports it, you can choose Run it in my terminal instead.

To ask another participant or an agent on their computer:

1. Open the panel picker (+) and choose People & agents. If that panel is already open, select its tab.
2. Find the participant. Click Ask beside an agent they made available, or beside Ask or delegate to [name] when you want the person to choose an agent or handle the request themselves.
3. Enter the request and click Send ask.

Nothing runs on another participant’s computer until they respond to Run this on your machine? with Allow. They can also click Decline. If you addressed the person rather than a named agent, they choose which available agent takes the request before allowing it. During an agent run, the session control shows Heard you… and then [agent] is working…. Click that status to open the conversation the ask started. Project owners and collaborators can send an ask to another participant’s computer. A Project Reader can join the desktop session and approve or decline an ask sent to them, but cannot successfully submit a remote ask. A Collaborator-link guest can see the desktop roster and offered agents, but the link alone does not grant permission to submit a remote ask. In both cases, Ask may appear and open the request composer even though Send ask cannot complete the request. Anonymous Reader-link guests stay in the browser view, which does not show People & agents or in-session agent controls.

​

Send from the desktop app

After a session ends:

1. Click Use this session in the floating session control.
2. Choose Send to AI agent. For a folder destination, the row reads Save context folder.
3. Choose a saved Handoff destination, or click Set up another destination….

For a whole Live Session, the setup screen also has a No setup needed section. Choose Ask Chief to continue in Chief, or Download session (.zip) to save the transcript, notes, and session files for upload to another AI chat. This section is not shown when you send only the items under one tag. On first use, Chief asks How do you use your agent?, then shows Review your setup. Choose an agent, project folder, folder destination, or custom command; optionally choose a harness; enter what the agent should do; select Transcript, Live notes, Captures, and Documents & canvases as needed; then click Save setup. If an imported Claude Code or Codex setup names a command-line tool Chief cannot start on this computer, Chief converts it to a folder destination named Context folder and explains that you can upload the files to any AI chat. While a session is running, click Send the session so far to an AI agent in the floating control. The modal explains that the agent gets the session so far while Chief keeps recording. This action is available to Project members, not guests or Collaborator-link participants.

​

Send from the web app

On a finished session, click Send to AI agent. Under What do you want made?, choose a suggested or fixed shape, add Instructions, then choose Chief or Any chat app under Send it to. Use Copy bundle or Save .md when you want a portable handoff. The session’s ⋯ menu also offers Download agent .md. The handoff can include the transcript, images, Live Notes, and documents or canvases.

​

Let the agent retrieve more context

The exported file identifies the Live Session and explains how an agent can use Chief’s MCP server or REST API for current or additional Project context. The export never embeds your Personal Access Token. If the agent needs access, create and provide credentials securely for the correct Project.

​

FAQ