Back to documentationCodex multi-agent guide

Orchestrate Sol and Terra agents in DCC

Use GPT-5.6 Sol as the primary agent, delegate independent work to Terra subagents, and supervise the complete flow from the DCC chat.

How orchestration works

Sol remains responsible for understanding the request, making decisions, integrating every required result and delivering the final response. When work can be divided safely, it can start Terra subagents in parallel.

  • Delegate independent research, review, testing and bounded implementation work.
  • Keep small, sequential or tightly coupled work in the primary thread.
  • Use the smallest useful team to avoid unnecessary latency and usage.

Install the orchestration preset

The preset is installed per project and compiled into the active worktree.

  1. 1Open the project in DCC.
  2. 2Open Skills.
  3. 3Click Orchestration preset.
  4. 4Keep the default values and confirm that Codex is selected under Target agents.
  5. 5Leave Disable model invocation turned off.
  6. 6Click Save skill.
  7. 7Create a new session after the button displays Orchestration installed.
Saving creates the dcc-orchestration skill and compiles it automatically. A session that was already open may have loaded the previous skill catalog.

Automatic and explicit activation

Select GPT-5.6 Sol from the model selector in the chat. You do not need to mention the skill in every prompt.

Automatic

Sol may invoke the skill when delegation materially improves speed, quality or context isolation. A simple task may stay in the primary thread.

Example prompt

Analyze the frontend and backend architectures independently, identify risks, and provide a consolidated recommendation. Do not modify files.

Explicit

Name the skill and request delegation when you want orchestration for a specific task.

Example prompt

Use $dcc-orchestration and delegate the independent parts to Terra agents.

You can also ask Sol to delegate without naming the skill. Explicitly naming it removes ambiguity about which workflow you want.

Configure concurrent subagents

Open Settings → Providers → Codex → Concurrent subagents. The setting applies to new sessions and does not count Sol.

Automatic (Codex)

DCC sends no concurrency limit and lets Codex decide.

Numeric limit

Restricts how many subagents may be open at the same time.

The preset normally starts one to three subagents and always respects the configured limit.

Quick test: verify Sol → Terra

Use this read-only flow to verify delegation without changing project files.

  1. 1Install the preset.
  2. 2Create a new session.
  3. 3Select GPT-5.6 Sol in the chat.
  4. 4Send the test prompt below.
  5. 5Expand Agent tree in the response.

Example prompt

Use $dcc-orchestration. Start two Terra agents in parallel: one should analyze only the frontend architecture and the other only the backend architecture. Do not modify files. Wait for both agents and provide a consolidated conclusion.

Expected result

  • Primary agent — GPT-5.6 Sol.
  • Two Terra subagents with their own names and paths.
  • Working while each subagent is running.
  • Completed or Failed when each subagent finishes.
  • The chat becomes available after Sol delivers the final response.

Test automatic activation

After the explicit test succeeds, create another Sol session and send a complex request without mentioning delegation or the skill.

Example prompt

Independently evaluate the frontend architecture, backend architecture, and test strategy. Compare the results and recommend the three most important improvements. Do not modify files.

If no subagent appears for a small request, that is not necessarily a failure. Use the explicit quick test to distinguish a model decision from an infrastructure issue.

Monitor and supervise

Agent tree shows every subagent started by Sol while keeping the primary agent visible.

  • Use Instruct to send additional guidance to an active subagent.
  • Use Interrupt to request that an active subagent stop.
  • Follow each agent's model, path and status.
  • Wait for Sol to integrate all required results and complete the primary response.
Older sessions that did not record a final subagent event may display Ended. This neutral historical status prevents DCC from incorrectly claiming that an agent is still working.

If no subagent appears

Check the session and preset before treating the behavior as a runtime failure.

  1. 1Confirm that GPT-5.6 Sol is selected in the chat.
  2. 2Confirm that Skills displays Orchestration installed.
  3. 3Confirm that Codex is a target agent.
  4. 4Leave Disable model invocation off for the automatic test.
  5. 5Create a new session after saving the skill or changing concurrency.
  6. 6Run the explicit quick-test prompt.
DCC detects whether the installed Codex CLI supports the orchestration capability used by the session. If it is unavailable, DCC preserves the previous behavior instead of breaking the session. Update the Codex CLI when a compatible version is available, then test again in a new session.