Helpers and sub-agents

A session can hand part of its work to a helper, so that its own conversation stays small. Claude Code, Codex and Grok can all do this when they judge it useful. The question for you is whether you can see those helpers and talk to them. In AigoPilot you choose, and the helpers are shown under the session that called them.

There are two kinds of helper, and the difference decides what you can do with them.

Subagent or separate session

For both, the helper starts with an empty context and knows only the prompt it is given. The quality of the work and the tokens it uses are about the same. Helpers that run at the same time spend the same subscription at the same time.

Choose how your sessions hand off work

Open Settings and find Handing work to helpers under How sessions work. There are three choices:

• Small: subagent, big: separate session is the default. The session judges which is which. A search or one fix is small; building a part, a long run, or work you may want to watch or steer is big.
• Always a separate session, so every piece of handed-over work stands in your list.
• Always a subagent, so helpers stay inside their session and your list does not grow.

The same choice, with its limits, is in the Helpers window under More in Settings, and it is offered once on first run. There you also set how many helper sessions one session may have open at once (3 by default) and whether a helper may open helpers of its own (off by default).

The choice counts for sessions you start or continue from then on; a running session keeps what it was told. It reaches Claude Code, Codex (through the studio's usual way of running it) and Grok. A session you start outside the studio, in VS Code or a terminal, cannot be told, and does what its own program does. Codex run in its older exec way is told nothing, and Claude Code in a console window of its own can use subagents but not separate sessions.

See the helpers under their session

A session that has helpers shows a chip with a count in its header, such as "1 helper session · 2 subagents". Click it and each helper is a row: a sign for how it stands (working, waits for you, finished, failed, stopped), its name or task, what it works with and what it spent. The cost line reads "This session: A, with its helpers: B".

A helper session opens as the session it is, and has a chip in its header, "Helper of ...", that takes you back to its parent. A subagent opens for reading only. You cannot write to a subagent. The session that is waiting for a helper says so, and when the answer arrives the conversation says that it went back.

How a separate session gets opened

A session asks the studio with a small program of its own, aigopilot-helper, and a brief written to a file. Because opening a helper is work inside the project, you are asked wherever commands inside the project are asked: in "Fully safe" mode every time. The card is called "Open a helper session?" and shows the name, the tool, the model and the brief, so you read what the helper will be told. See permission modes.

The helper works in the same project, with the account and the permission mode of the session that opened it, and its own tool calls are asked one by one like any other. What it spends is counted under its own name on the usage page. If you want it to stop, stop it like any session: stopping a session.

The answer of a helper comes back to the session that waits for it by itself. If that session is not running, the answer waits in its line of prompts until you continue it.

Small tips

Questions