SecondBrain
Ask the Brain
Index/Entityupdated Sat Jun 13 2026 08:00:00 GMT+0800 (Philippine Standard Time)

Claude Code

toolagentanthropicclaude-codellmmeta-agent

Claude Code

Anthropic's coding agent. Originated in Anthropic Labs (late 2024) under Boris Cherny. The agent currently maintaining this Second Brain.

Origin & inflection (per Boris Cherny on Coding Is Solved (Sequoia AI Ascent))

  • Built pre-PMF for ~6 months because Boris bet the next model would unlock agentic coding
  • State of the art at launch was tab-complete (Sonnet 3.5)
  • PMF inflection: Opus 4 in May 2025, kept inflecting through 4.5 → 4.6 → 4.7
  • Codebase: TypeScript + React (chosen because most on-distribution for the model in late 2024)

Role in this wiki

  • The maintainer. This vault's CLAUDE.md is the schema Claude Code reads when ingesting/querying/linting. See LLM Wiki Pattern and Harness (LLM Agents).
  • Karpathy's gist (LLM Wiki (Karpathy gist)) lists Claude Code as one of the canonical agents this pattern is designed for.

Surfaces

  • CLI — original surface; majority of Boris's audience uses it
  • Desktop app — secondary
  • iOS app — Boris's primary surface in 2026 (5–10 sessions, hundreds of agents)
  • VS Code / JetBrains plugins — minority usage per Boris's poll
  • Routines — server-side scheduled agents (don't need laptop open)

Extension surfaces relevant to this wiki

  • CLAUDE.md — per-project schema/instructions; the load-bearing config for this vault
  • Skills — invokable workflows (e.g. the Printing Press factory ships as a skill); self-improvable via auto-research loops over Binary Eval Assertions — see Skills (Claude Code)
  • MCP servers — alternative tool-loading mechanism; criticized in CLI vs API vs MCP for context bloat
  • /loop — schedule a recurring cron job (Boris Cherny: "loops are the future")
  • /batch — parallel agents
  • Sub-agents — agent-spawned-by-agent
  • Workflows / Ultracode — a planning agent that fans out to hundreds of parallel sub-agents (e.g. one per file for a whole-codebase review). MYTHOS MYTHOS MYTHOS (Matthew Berman) watched 63 agents run in parallel for a single build and 100+ for a codebase review; Fable 5 is described as especially good at exploiting it. The product-level instance of the multi-agent / sub-agent loop.
  • Hooks, slash commands, settings.json — other knobs (not yet used in this vault)

Boris's workflow (canonical example of agentic engineering at scale)

  • Most work from his phone via the Claude iOS app
  • 5–10 sessions, several hundred agents running at any time
  • Overnight: a few thousand agents on deeper work
  • Dozens of /loop jobs running: babysitting PRs (auto-rebase, fix CI), keeping CI healthy, clustering Twitter feedback every 30 min

"There was a day last week I did like 150 PRs in a day. That was a record."

Cross-source observations

All five ingested sources treat Claude Code as the default agent — it's the hub entity in this wiki. Both Andrej Karpathy (calls it the canonical Software 3.0 agent) and Praveen Akkiraju (calls it a "very well-defined harness") reference it explicitly. The product-vs-model attribution Boris discusses (50/50 in the early days, model-leaning over time) is a useful frame for any agent-product analysis.

The IC / non-engineer view (Sandeep)

How To Use Claude Better Than 99% Of People (theMITmonk) reframes Claude as a five-surface product stack rather than just the CLI tool, aimed at the consultant / business-user / IC operator audience (the complement to Boris's CLI-engineer audience):

Surface Activity Sandeep's pitch
Claude Chat Think Messy problems, fuzzy ideas
Claude Projects Remember Persistent context across sessions; user customizes at project level, not account
Claude Cowork (desktop) Execute Multi-step tasks with local-disk output; sandbox to a specific folder
Claude Code Build "If you can type in English, you don't need a CS background" — vibe-coding for the non-engineer
Claude Chrome (extension) Browse Acts inside the browser workflow — job listings, industry reports, forms

Plus Skills (repeatable workflows) and MCP connectors for fan-out to other tools. Worked example in the video: Cowork + MCP → Higgsfield for ad-creative generation.

This view is structurally distinct from Boris's "I do 150 PRs a day from my phone" CLI worldview — but both are valid; the stack frame lands for users whose work doesn't fit a code-PR shape.

As an operating system (Nate Herk)

I Turned Claude Opus 4.8 Into My Entire AI Operating System (Nate Herk) pushes the surface-collapse one step further than Sandeep: instead of a 5-surface stack, work out of Claude Code by default for everything (the Default Shift) so context compounds in one place. The OS is just files/folders → tool-agnostic across Claude Code / Codex / OpenClaw. Built via the Four C's Framework; governed via the Bike Method and Capabilities vs Instructions (Agent Keys). See AI Operating System (AIOS).

Counterpart at the other lab

Codex (OpenAI) is the structural twin of Claude Code. Ryan Lopopolo's Harness Engineering (Ryan Lopopolo, AI Engineer) talk describes a workflow nearly identical to Boris's — full-send agentic engineering, no editor use, hundreds of agents running, harness as the leverage point. The choice of lab matters less than the discipline around it. Lopopolo's prescription to depend on first-party harnesses directly via SDK or CLI (to ride the post-training leverage the labs invest in their own apply-patch / bash-invocation semantics) applies equally to Claude Code and Codex.

2026-06-13 — writes most of Anthropic's own code (Economist)

Per How AI Got Better at Building Itself (Economist), Claude Code now writes >80% of Anthropic's own published code (up from low single digits). This makes it the most direct corporate instance in the Recursive Self-Improvement argument — the lab's own development loop is now majority-agent-written, the scaffolding building the next generation of the scaffolding.

2026-06-27 — separated from Cowork in Anthropic's own usage data

Anthropic Economic Index Cadences Report (June 2026) is the first time Anthropic publishes usage data with Claude Code split out as its own cohort (alongside Claude Cowork and 1P API). The artifact-mix difference is the headline:

  • Cowork (with chat) — dominated by explanations and guidance (~⅓ of artifacts)
  • Claude Code — much more code and technical artifacts

This is the data-side confirmation of the surface-split this page has tracked since Sandeep's 5-surface view — and it now shows up in Anthropic's own analytics, not just in the product UI. See Claude Cowork for the sibling page; see Artifacts (Claude Output) for the classification primitive Anthropic uses to make the split visible.

Sources