---
id: "entity-claude-code"
type: "entity"
entityType: "tool"
canonicalName: "Claude Code"
canonicalUrl: "https://claude.com/claude-code"
source_timestamps: ["§4.1"]
tags: ["tool", "agent-runtime", "model"]
related: ["concept-icm", "framework-icm-architecture"]
aliases: ["Claude Opus 4.6", "Claude Sonnet 4.6", "Claude Code"]
sources: ["paper"]
sourceVaultSlug: "icm-paper-folder-architecture-2026Jun02"
originDay: 2
---
# Claude Code (Opus 4.6 + Sonnet 4.6)

## What it is

The **sole agent runtime** used to develop and run all ICM workspaces. From Anthropic.

- Primary orchestrating agent: **Claude Opus 4.6**.
- Subagent workers: **Claude Sonnet 4.6**.

## How it interacts with ICM

Within a stage, the orchestrating Opus agent **delegates sub-tasks to faster Sonnet 4.6 subagents** — delegation itself driven by the folder structure (the agent reads the stage's `CONTEXT.md` to decide what to delegate and what context to provide). See [[framework-icm-architecture]].

## Important nuance: single-orchestrator, not single-agent in execution

This means ICM is **single-ORCHESTRATOR with folder-driven subagent delegation**, not strictly single-agent in execution.

The paper's claim is precisely **"no orchestration framework,"** not **"no second model."** The extraction notes this explicitly, and it should not be over-simplified when summarising. The mechanism is unchanged: only files differ between stages — see [[quote-folder-controls-context]].

## Limitation

All testing used this single Claude model family — whether ICM generalizes to other families (GPT-4 class, Gemini, Llama) is the open question [[question-cross-model]].


## Related across days
- [[entity-claude]]
- [[entity-anthropic]]
- [[synthesis-single-agent-clarified]]