Explains why Claw Code is closer to a coding agent runtime than a simple chat CLI by looking at repository boundaries, Rust workspace design, the Python reference layer, and parity validation.
Breaks down how a command travels through parsing, LiveCli assembly, session/config/permission/sandbox setup, and ConversationRuntime to complete a full agent turn.
Explains how Claw Code separates tools, skills, and slash commands into three layers and extends them into platform capabilities like plugins, MCP, workers, cron jobs, streaming, and telemetry.
Explains how Claw Code manages long context through session transcripts, project context, prompt budgets, prompt cache, and session compaction instead of vector-memory retrieval.