Skip to main content
In complex tasks, the main Agent can hand off the parts that can run in parallel. AIHubMix Cloud offers two forms:
  • Subagents: helpers the main Agent starts within the same session. The session shows only one extra progress row, and you can view the work read-only in the subagent tab of the right drawer.
  • Child sessions: separate sessions the Agent starts. Each child session has its own row in the sidebar, nested under the parent session, and you can open it and handle its approvals separately.
Both differ from a Fork you create manually: a fork is a regular session. See Messages and session actions.

Availability

Subagents

Subagent names and shapes

Each subagent gets a name in the order it is started (Coral, Lagoon, Iris, Lime, Amber, Sky; after 6, a number is added, for example Coral 2) and a matching colored shape, which stay fixed within the session. A running subagent has a thin rotating arc around its shape. The shape appears in the subagent row in the session, the steps it owns in the plan, the task summary card, the drawer tab, and the file source markers in Changes.

One extra row in the session

When the main Agent starts subagents, only one row is added in the process area. Several subagents started together share one row. Hover a shape to see “name · task”, and click it to open that subagent’s tab in the right drawer.

Subagents run in the background

After starting subagents, the main Agent can continue its own part without waiting for them.
  • When the main Agent’s turn ends while subagents are still running, the timer row shows Worked for Ns, but the process stays expanded and the subagent row keeps updating.
  • You can keep sending messages at this point without waiting for the subagents.
  • After all subagents end, the platform automatically has the main Agent start a new turn to merge the results. When the task summary card is closed, a green dot appears on the top bar button.

Subagent tab

Click a subagent shape, or pick it from the drawer’s + menu, to open that subagent’s tab in the right drawer. The tab shows, from top to bottom:
  1. Name, task, and status (Queued / Running / Done / Stopped / Failed).
  2. The model and reasoning effort used, and the time taken.
  3. The full task description the main chat gave it.
  4. Activity: each step it took. Failed steps use a warning icon.
  5. Its changes: the files it changed and the lines added and removed. Click a file to open it in Files.
  6. Result (after it ends): the conclusion handed back to the main chat, or details on why it stopped or failed.
  7. Stop and Show in chat at the bottom.
  • The subagent tab is read-only, and you cannot send it messages there. To adjust its work, tell the Agent in the main chat.

View in the task summary card and Changes

  • The Subagents section of the task summary card shows all subagents and their progress. In the Plan section, each step shows the subagent that owns it on the right. For the full card description, see Understand the Agent’s output.
  • In the Changes tab, each file is marked with the subagent or main Agent that last changed it.

Child sessions

A child session is a separate session started by the Agent. It has its own row in the sidebar, and you can open it, handle its approvals, and stop it separately. Child sessions can also start their own child sessions.

Spawn card in the parent session

When the Agent starts child sessions, a Spawned N sub-sessions card appears in the parent session, with one row per child session. Click a row to open that child session. This card stays visible after the run collapses. After each turn of a child session ends, a note appears in the parent session, for example “Check Web settings page regression” finished: 28 checks passed, reported back, or that it stopped, failed, needs you, and so on.

Two levels in the sidebar

  • Child sessions are nested under the parent session. Click the count at the end of the parent session row to expand or collapse them.
  • Up to 2 levels are shown: parent session → child session → grandchild session.
  • When expanded, child sessions that have not ended, such as running or waiting for you, are listed directly. Ended ones collapse into one row, N completed; click to expand it.
  • The Pinned group does not fold child sessions. The status rules at the end of rows are the same as for regular sessions. See Sidebar.

Child sessions show who started them

When you open a child session, Spawned from “parent session title” appears next to the title in the top bar. Click it to return to the parent session. You can also use Go to parent chat in the command menu (⇧⌘P). When the parent session has been deleted, it shows Spawned from another chat.

Moving and approvals

  • When you move the parent session to a project, its child sessions move with it. Child sessions cannot be moved on their own.
  • Approvals in child sessions work the same as in regular sessions. See Needs your input.

FAQ

Can I keep chatting while subagents are running?

Yes. Once the main Agent’s turn ends, you can keep sending messages. After all subagents end, the main Agent automatically starts a new turn to merge the results.

Can I give instructions directly to a subagent?

No. The subagent tab is read-only, so tell the Agent in the main chat. To stop a subagent, click Stop at the bottom of its tab; its finished changes are kept.

What is the difference between subagents and child sessions?

Subagents run within the same session, and you view their work read-only. Child sessions are separate sessions with their own rows in the sidebar, and you can open them and handle their approvals separately.

Why are child sessions missing from the sidebar?

Parent sessions collapse their child sessions by default. Click the count at the end of the parent session row to expand them. Ended child sessions are further collapsed into an N completed row.