OPEN TEXTBOOK · ATLAS · LABORATORY

Open the agent shell.See the real system.

The model is only the engine. Study the harness that lets a coding agent read code, call tools, enforce permissions, manage context, and finish reliably.

13 runnable lessons0 API keys required11 replayable events
MECHANISM / agent-loop executable
01Intentuser.message
02Modelrequest / response
03Policyvalidate / authorize
04Tooleffect / result
05Contextappend / prune
HARNESSowns the loop
RUNNABLEVERSIONEDEVIDENCE-BACKEDREPRODUCIBLEBEGINNER → RESEARCHER
ONE CONTENT GRAPH · FOUR VIEWS

Not a pile of links.
A knowledge infrastructure.

Lessons, mechanisms, agents, claims, experiments, and traces connect through stable IDs. Pages are views; the Registry is the fact layer.

01

Academy

Build from zero

Thirteen runnable lessons, from loops and context to approval, sandboxing, and rollback.

02

Mechanisms

Compare designs

Organized by shared problems such as loops, context, tools, and safety.

03

Atlas

Versioned records

Every architecture fact is bound to an agent snapshot and surface.

04

Lab

Reproduce experiments

Pin fixtures, variables, traces, and failed runs.

FOUNDATIONS → SAFETY · S01—S13

Build one yourself
before judging any agent.

View the learning path
S01

The Minimal Agent Loop

Turn one model call into a loop with an explicit stop condition.

agent-loop
S02

Streaming and Events

Convert streaming deltas into observable, replayable events.

agent-loop
S03

Tool Registry and Dispatch

Validate, execute, and record model-requested tool calls.

agent-loop
S04

File, Shell, and Edit Tools

Put workspace boundaries and explicit allowlists around side-effecting tools.

workspace-tools
S05

Instructions and Project Discovery

Compose hierarchical instructions from the workspace root to the current directory.

instruction-discovery
S06

Context Budgets and Truncation

Make input pruning and tool-output truncation explicit policies.

context-budget
S07

Session Event Logs, Replay, and Branching

Rebuild derived state from append-only events and create lineage-preserving branches.

event-stream
S08

Context Compaction and Checkpoints

Replace long visible history with a provenance-bearing semantic checkpoint while retaining the factual log.

context-budget
S09

Memory and On-Demand Skills

Move durable facts and full capability instructions out of resident context, retrieving them only when relevant.

memory-retrieval
S10

Approval Policy and Exact Authorization

Insert fail-closed allow, ask, and deny decisions between model requests and real effects.

execution-policy
S11

OS Sandboxes and Network Boundaries

Compile semantic authorization into a minimal capability envelope enforceable by an isolation backend.

execution-policy
S12

Project Trust and Prompt Injection

Separate workspace identity, explicit trust, and instruction-versus-data authority.

project-trust
S13

Git Checkpoints, Diffs, and Rollback

Create a clean baseline before effects, review the exact diff, and roll back only explicit paths.

checkpoint-rollback
CLAIM → EVIDENCE → SNAPSHOT

Turn hearsay into inspectable claims.

OFFICIAL DOC2026-08-10
Claude Code's official Agent Teams documentation describes experimental lead-and-teammate coordination with independent context windows, a shared task list, direct messaging, and no automatic worktree isolation.
CLAIMclaude-code-doc-agent-teams
SNAPSHOTclaude-code-2026-08-10-docs
STATUSreviewed
Inspect the evidence boundary

Four evidence types, never conflated

01source

Pinned commit and source locator

02official-doc

Official vendor or project documentation

03reproduced

Reproduction in a pinned environment

04inference

Explicit interpretation and unknowns

TRACE 0.1 · CONTROLLED

A formal controlled experiment, event by event

SESSIONevt-000T+00:00:00Z

session.start

Actor reference-agent produced sequence 0. Redaction status is clean.

{
  "max_turns": 8,
  "tool_count": 3
}

1 events are visible; hidden chain-of-thought is not part of the trace.

Download JSONL
THE V0.1 PUBLIC PREVIEW IS RUNNING

Understand one mechanism. Run one trace.
Then go deeper into the source.

Start with s01Open the Experiment Lab