If you have heard the phrase "agentic coding" at all in the last year, you have heard about Claude Code. It started as one engineer's weekend experiment in September 2024, launched quietly in February 2025, and by early 2026 had become — per reporting on Anthropic's own numbers — one of the fastest-growing software products ever shipped, on its way to a multi-billion-dollar run rate and rewriting how software teams work.
This is the complete story: what Claude Code actually is, where it came from, how the agent loop works under the hood, the leak that showed everyone the internals, the ecosystem of skills and subagents and workflows that grew around it, and the honest answer to the question most explainers skip — should you, personally, be using it?
TL;DR: Claude Code is Anthropic's agentic coding tool: an AI agent that reads your codebase, edits files, runs commands, and iterates until the task is done. Launched February 24, 2025; ~$2.5B annualized revenue by February 2026, per public reporting. If you don't write code, the same agentic pattern powers Taskade Genesis — apps, agents, and automations from one prompt.
🤖 What Is Claude Code, Exactly?
Claude Code is an AI agent that works on your computer, not a chatbot that talks about your code. You give it a task in plain English — "fix this failing test," "migrate this component," "find out why signups dropped" — and it searches your files, makes edits, runs commands, reads the output, and keeps going until the job is done or it needs your approval. It lives in the terminal first, with IDE extensions, a desktop app, and a web version layered on top.
The distinction that matters on day one:
| Claude (chat) | Claude Code | Claude Cowork | Claude Agent SDK | |
|---|---|---|---|---|
| What it is | AI assistant in a chat window | Agent that acts on your codebase | Agent for everyday office work | Toolkit to build your own agents |
| Where it runs | claude.ai, apps | Terminal, IDE, desktop, web | Desktop | Your own product |
| Output | Answers and artifacts | Edited files, commits, running code | Documents, spreadsheets, files | Whatever you build |
| Who it's for | Everyone | People who ship software | Knowledge workers | Developers building agents |
That second column is the subject of this post. And the fastest way to understand why it exploded is the principle its creator names as the most important one in product:
"Latent demand I think is the single most important principle in product. You can never get people to do something they do not yet do. The thing you can do is you can find the intent that they have and then you can steer it." — Boris Cherny, creator of Claude Code
Developers were already pasting code into claude.ai and wiring the API into their editors. Claude Code didn't invent a behavior — it removed the friction from one that already existed.
⚡ How Claude Code Actually Works
Under the hood, Claude Code is a loop: gather context → act → verify → repeat. The model decides which tool to use next — read a file, search the codebase, run a command — looks at the result, and chooses the next step. Everything else (skills, hooks, subagents, workflows) is scaffolding around that loop.
Three design decisions defined it, all confirmed by the team on the record:
1. Search like an engineer, not like a search engine. Early Claude Code used vector embeddings to find relevant code — the standard "RAG" approach. The team ripped that out in favor of agentic search: the model greps and navigates files the way a human would. Accuracy stayed the same, and an entire class of problems (stale indexes, re-indexing, a bigger security surface) disappeared.
2. Give the model everything, mediated by permissions. As the team puts it: Claude Code has access to everything an engineer does at the terminal — "everything you can do, Claude Code can do." What keeps that safe is a permission system that asks before risky actions, with rules you can tighten or loosen per project.
3. "Don't build for the model of today. Build for the model 6 months from now." Cherny's design maxim explains the product's strange minimalism. The team once deleted about 2,000 tokens of instructions from the system prompt because a newer model no longer needed them — in their words, "models will eat your scaffolding."
The vocabulary you'll meet everywhere, in one table:
| Concept | Plain-English meaning |
|---|---|
| CLAUDE.md | A text file of project rules the agent always reads — its durable memory of your conventions |
| Plan Mode | The agent proposes a plan before touching files; the team says planning first can 2–3x success rates |
| Skills | Folders of instructions that teach repeatable workflows, loaded only when relevant |
| Hooks | Scripts that fire on events (before a command, on finish) — guardrails and notifications |
| Subagents | Helper agents with their own separate context windows for delegated work |
| MCP | An open protocol for connecting outside tools and data sources to the agent |
🥚 The Origin Story: A Weekend Project and a Research Tool Called Clyde
Claude Code began in September 2024 as a side project by Anthropic engineer Boris Cherny. By his own account, the idea was almost naive: "let me just see if I can build a thing where you can give Claude access to your terminal and your file system and it can just help you code." The first version, he says, "was terrible." But it showed signs of life, internal demand snowballed, and a team formed around it.
According to the team's own telling, there was a precursor: a heavyweight internal Python research project the engineers describe under the name Clyde. Cherny joined Anthropic, hand-wrote a pull request, and was told to try the internal tool instead — which completed the task in one shot. The revelation that stuck, in the team's words: "the model just wants to use tools." Given nothing but a shell, the model started writing AppleScript to automate the computer. The terminal interface wasn't a philosophical statement — it was simply the fastest way to prototype without building a UI.
Cherny's own path to that weekend project reads like preparation in hindsight: years at Meta (including the two-year facebook.com rewrite and growth work at Instagram), the O'Reilly Programming TypeScript book, and a habit of building developer tools nobody asked for. Anthropic's flat structure did the rest — everyone from engineers to PMs carries the same "Member of Technical Staff" title, a convention borrowed from Bell Labs, and the Claude Code team recruits generalists ("our product managers code, our data scientists code").
The features you now think of as the product arrived bottom-up, built by individual engineers scratching their own itches: todo lists (Sid), hooks (Dixon), plugins (Daisy), bash mode (Cherny himself). Hooks exist because engineers wanted a Slack ping when Claude was waiting for permission while they got coffee. Internally, the feedback channel gets a post roughly every five minutes — Anthropic calls the practice "ant-fooding."
"When I created Claude Code as a side project back in September 2024, I had no idea it would grow to what it is today... This technology is alien and magical, and I feel lucky to experience it so intimately." — Boris Cherny
📜 The Complete Timeline: 2024–2026
From side project to multi-billion-dollar product line in under two years. Every date below is drawn from Anthropic announcements, official docs, or named press reporting.
| Date | Event |
|---|---|
| Sept 2024 | Boris Cherny starts Claude Code as an internal side project |
| Feb 24, 2025 | Research preview launches alongside Claude 3.7 Sonnet |
| Apr 2025 | Source-map leak exposes ~390K lines of the TypeScript source (more below) |
| May 22, 2025 | General availability at Code with Claude, Anthropic's first dev conference |
| June 2025 | Included in the $20/month Pro plan |
| July 2025 | Cherny and product lead Cat Wu leave for Cursor-maker Anysphere — and are back at Anthropic ~2 weeks later (The Information) |
| Oct 2025 | Agent Skills launch as an open standard; skills directory; org-wide management |
| Nov 2025 | ~$1B annualized revenue, ~6 months after GA (press reporting) |
| Feb 2026 | ~$2.5B annualized revenue — roughly doubling in three months (press reporting) |
| Mar 23, 2026 | Computer use lands in Claude Code and Claude Cowork; scheduled tasks run on managed cloud |
| May 28, 2026 | Dynamic workflows ship in v2.1.154, alongside Claude Opus 4.8 |
The July 2025 detour deserves its own sentence, because it was the AI talent war in miniature: Anysphere hired away the two people most identified with Claude Code — Cherny as chief architect and head of engineering, Wu as head of product — and two weeks later both were back at Anthropic. Few episodes say more about how strategically important agentic coding had become by mid-2025.
For the wider company story — the founding, the funding, the model generations — see our full Anthropic and Claude history.
💥 The April 2025 Leak: Everyone Got to Read the Source
Two months after launch, Anthropic accidentally published Claude Code's source. An npm release shipped with source maps included, exposing roughly 390,000 lines of TypeScript across ~2,000 files — and because hundreds of other packages already depended on the release, npm policy blocked unpublishing it.
Everything "known" from the leak is community analysis rather than official documentation, so treat the details accordingly. But the reported architecture became required reading for anyone building agents:
- One loop, not a framework. The internals community analysts described were a single agent loop with tools — no exotic multi-agent choreography. A Reddit post claiming to have reverse-engineered a secret "multi-agent framework" from the leak was debunked; the durable insight was the opposite: the simple thing works.
- Layered permissions. Analysts described a multi-level permission cascade (policy → flags → local → project → user) mediating everything the agent does.
- Context is managed obsessively. CLAUDE.md is reportedly re-inserted as context changes rather than pasted once; multiple compaction strategies keep long sessions alive.
The leak's real legacy was a mental-model shift the industry now takes for granted: the harness matters as much as the model. The same model, wrapped in different scaffolding, produces meaningfully different outcomes — which is why every serious AI lab and tool company now competes on the loop, the permissions, the memory, and the context management, not just the weights. (Our agent harness explainer goes deep on that idea.)
🧠 The AI Layer: CLAUDE.md, Skills, Hooks, and Subagents
By 2026, Anthropic's own guidance treats the "AI layer" as a first-class part of a codebase — alongside the code and the tests. That layer is the accumulated instructions, rules, and workflows that make an agent effective in your project rather than generically smart.
A modern codebase, 2026:├── src/ ← the code
├── tests/ ← the tests
└── the AI layer
├── CLAUDE.md ← project rules, always loaded
├── src/api/CLAUDE.md ← area-specific rules, loaded in place
├── .claude/skills/ ← repeatable workflows, loaded on demand
├── .claude/hooks/ ← guardrails that fire on events
└── MCP servers ← connections to outside tools
Two mechanisms make the layer economical:
Progressive disclosure. A skill costs the agent only its name and description — tens of tokens — until the task makes it relevant, at which point the full instructions load. You can attach dozens of workflows without drowning the context window. The same philosophy shows up in Anthropic's Tool Search Tool, which loads tool definitions on demand and cut context usage from 77,000 tokens to 8,700 in Anthropic's published example.
Self-improvement hooks. Anthropic's large-codebase guidance describes a pattern where a hook fires when a session ends, spawns a fresh headless agent to review what happened, and proposes CLAUDE.md updates while the context is still warm. Correct the agent once, and the correction compounds.
Does the AI layer actually work? The best independent evidence so far: an ETH Zurich study (arXiv 2602.11988, February 2026) tested agent/model pairs with and without context files and found developer-written files helped, while auto-generated ones were a small net negative — they added bloat without adding judgment. Write your CLAUDE.md by hand.
And subagents earn their keep for one non-obvious reason the team states plainly: uncorrelated context windows produce better results. Two agents that can't see each other's reasoning don't share each other's blind spots — the same reason you ask two people to review a document independently. For the concept in depth, see our Claude skills explainer and the tested skills roundup.
🕸️ Dynamic Workflows: The Orchestration Era (May 2026)
On May 28, 2026, Claude Code stopped being one agent. Dynamic workflows, shipped in v2.1.154 alongside Opus 4.8, let Claude write a real orchestration script — actual JavaScript with loops and conditionals — that fans out subagents, collects their results, and controls the flow deterministically: up to 16 agents running concurrently, 1,000 per run.
The official docs give the crisp reason this exists: "A workflow script holds the loop, the branching, and the intermediate results itself, so Claude's context holds only the final answer." One long-running agent past a few hundred thousand tokens develops predictable failure modes — the community shorthand is agent laziness (claims all fifteen tasks are done, did seven), self-preference (grades its own homework kindly), and goal drift. Orchestration sidesteps all three by making the structure external to any single context window.
The flagship demonstration arrived within weeks: Bun creator Jarred Sumner used workflow-orchestrated Claude Code to port the Bun runtime from Zig to Rust — roughly 750,000 lines of Rust by the official account (The Register counted "over one million lines" across ~6,755 commits in the raw diff), with 99.8% of the test suite passing. Reasonable people can argue about what the port proves; nobody argues it was possible for one person before.
The cost honesty that belongs next to the excitement: Anthropic's own engineering blog reports agent systems use roughly 4x the tokens of chat, and multi-agent systems roughly 15x. Orchestration is a power tool, priced like one.
📈 Claude Code by the Numbers (Mid-2026)
The growth curve is the story. Figures below are from Anthropic statements or named reporting; treat third-party estimates as estimates.
| Metric | Figure | Source |
|---|---|---|
| Annualized revenue, Nov 2025 | ~$1B (~6 months post-GA) | press reporting |
| Annualized revenue, Feb 2026 | ~$2.5B | press reporting |
| Anthropic staff using it daily | 80% | Anthropic, Sept 2025 |
| Share of public GitHub commits | ~4% | third-party usage analyses, mid-2026 |
| Autonomous task horizon (Opus 4.5) | ~4h49m at 50% completion | METR, Dec 2025 |
| Anthropic ARR context | ~$1B (Dec '24) → ~$14B (Feb '26) → ~$19B (Mar '26) | per SaaStr/Meritech |
Cherny's most striking internal claim — that Anthropic tripled in headcount while productivity per engineer still grew about 70% because of Claude Code — is a company self-measurement, but it matches the external evidence: he has publicly described landing 259 PRs in 30 days with every line written by the agent.
💼 Beyond Coding: The Claude Code Economy
The most surprising 2026 development is who uses Claude Code now. An agent loop that can run a long time, touch files, and reach the internet turns out to be a general-purpose work engine, and a creator economy has grown around treating it as one:
- Business operating systems. Course creator Nate (who says he built a $100K/month automation agency) teaches an "AIOS" — a portable brain of context files and skills. His system is deliberately tool-agnostic: the durable asset is the markdown, not the harness; he claims porting an entire setup from Claude Code to Codex took two minutes. His best line doubles as a philosophy: "Treat AI as a mentor, not a vending machine."
- SEO at scale. One practitioner attributes ~50,000 monthly clicks to a Claude-Code-driven publishing pipeline — blog posts for topical authority, service pages for money keywords. (Claims are the creator's own.)
- Faceless YouTube. A channel reportedly hit 130K subscribers and 14M views in about a month with a Claude Code + image-generation pipeline; the revenue estimates ($60K+/month) come from VidIQ, not audited books.
- A YC-endorsed software factory. Y Combinator president & CEO Garry Tan open-sourced gstack, a 28-command sprint process for Claude Code (Think → Plan → Build → Review → Test → Ship → Reflect) with a doctrine worth stealing: "Boil the Lake" — when AI makes completeness nearly free, always do the complete thing.
- Second brains. Andrej Karpathy popularized a no-vector-database pattern: an Obsidian vault of markdown plus Claude Code as the librarian — plain files, grep, and an index note instead of embeddings. Thousands now run it.
Anthropic institutionalized the trend by renaming the Claude Code SDK to the Claude Agent SDK — per the team, thousands of companies build non-coding agents (health assistants, financial analysts, legal research, email) on the same loop. It is the clearest signal of where this goes: the coding tool was the beachhead; the agent loop is the product. Our execution layer thesis explores that shift.
⚔️ Claude Code in the 2026 Landscape
Nobody picks an agentic coding tool in a vacuum anymore. The honest mid-2026 map:
| Tool | What it is | Strongest at | Trade-off |
|---|---|---|---|
| Claude Code | Terminal-first agent | Long agentic runs, customization depth | No free tier; terminal comfort assumed |
| OpenAI Codex | Agent in the ChatGPT ecosystem | Bundled pricing, unified shipping | Less extensible |
| Cursor | AI-native editor | Staying in a familiar IDE | You drive; less autonomous |
| OpenClaw | Open-source always-on agent | Personal automation, 24/7 presence | You run and secure the server |
| Gemini CLI | Google's terminal agent | Generous free tier | Younger ecosystem |
Benchmarks won't settle it for you: by mid-2026, frontier models sit in a tight band on SWE-bench Verified, so harness fit — how the tool matches your workflow — matters more than leaderboard deltas. The deep dives: Claude Code vs Codex, Claude Code vs Cursor vs Taskade Genesis, Claude Code vs OpenClaw, Claude Code vs n8n, and the full alternatives roundup.
Which plan do you actually need?
Claude Code has no free tier. The ladder, at 2026 prices: Pro $20/month (entry, with usage windows heavy users outgrow), Max $100/month (5x limits), Max $200/month (20x limits), or metered API pricing — where a typical 200K-token run costs roughly $0.20–$2.00, and heavy orchestration costs multiples of that. Practitioner rule of thumb: Pro to evaluate, Max when it becomes your daily driver, API when you're building on the Agent SDK.
🛑 When NOT to Use Claude Code
An honest section most explainers skip. Claude Code is the wrong tool when:
- You don't read code. The product assumes you can judge a diff. "Vibe-coding" past that assumption is how people ship things they can't maintain — the failure mode isn't the tool, it's the unreviewable output.
- You need predictable costs. Agentic runs are token-hungry by design (4x chat, per Anthropic; 15x for multi-agent). Budget-capped teams feel this fast.
- The task is a repeatable business workflow, not a coding project. "Every Monday, summarize support tickets and post to Slack" doesn't need a terminal agent wired to a codebase — it needs an automation with a trigger, and maintaining a script + server + API keys is real overhead for a non-engineer.
- The output must be right the first time, unreviewed. Non-deterministic generation plus no review gate is a production incident with extra steps.
🧑🚀 If You Don't Write Code: The Same Power, a Different Door
Here's the convergence that makes 2026 interesting: the agent pattern Claude Code proved out is not inherently about code. An agent that reads and writes files, remembers your conventions, delegates to helpers, and executes multi-step work — that pattern applies to any structured workspace.
That's precisely what Taskade Genesis does for people who will never open a terminal: describe what you need in plain English, and it builds a live app backed by your workspace — with AI agents (34 built-in tools, persistent memory), automations across 100+ integrations, and databases, running on managed infrastructure with team permissions instead of a server you harden yourself. The same loop; the door is a prompt instead of a shell. Where Claude Code turns a developer into a team, Taskade Genesis turns a description into a working system — and 150,000+ apps in, the pattern holds. Explore what people build in the Community Gallery, or start free at taskade.com/create.
The two tools don't compete so much as bracket the same future from opposite ends: software that builds and runs itself, supervised by the person who needed it. Memory feeds intelligence, intelligence triggers execution, execution becomes memory. ▲ ■ ●
💬 Frequently Asked Questions
What is Claude Code in simple terms?
It's an AI agent from Anthropic that does programming work on your computer. You describe the task; it reads your project, edits files, runs commands and tests, and iterates — asking permission before risky steps — until the work is done.
When did Claude Code come out?
February 24, 2025 as a research preview (alongside Claude 3.7 Sonnet), with general availability on May 22, 2025 at Anthropic's Code with Claude conference.
Who invented Claude Code?
Boris Cherny started it as an internal Anthropic side project in September 2024; Cat Wu led product. The team openly credits individual engineers for signature features — hooks, plugins, todo lists — built bottom-up.
How much does Claude Code cost in 2026?
$20/month (Pro), $100/month (Max 5x), $200/month (Max 20x), or metered API pricing where a 200K-token run costs roughly $0.20–$2.00. There is no free tier.
Is Claude Code an IDE?
No. It's an agent that runs in your terminal and integrates with IDEs (plus desktop and web apps). You can use it inside editors like VS Code or Cursor, but it isn't an editor itself.
What models does Claude Code use?
Anthropic's Claude family — with the model selectable per session and the tool designed, per its creator, "for the model 6 months from now" so it improves as models do.
What is the Claude Agent SDK?
The renamed Claude Code SDK: the same agent loop packaged for developers to build their own agents. Anthropic renamed it after thousands of companies used it for non-coding agents in health, legal, finance, and research.
What happened when Claude Code's source code leaked?
An April 2025 npm release accidentally included source maps, exposing ~390K lines of TypeScript. Community analysis described a single agent loop with layered permissions and careful context management — reinforcing the industry lesson that the harness matters as much as the model.
Can Claude Code work on things that aren't code?
Yes — research, writing, file organization, publishing pipelines, personal knowledge bases. A whole creator economy (business "operating systems," SEO pipelines, YouTube channels) runs on it. But the interface still assumes terminal comfort.
What should non-developers use instead of Claude Code?
An AI workspace that runs the same agentic pattern without a terminal. Taskade Genesis builds live apps with agents, automations, and databases from a plain-English prompt, on managed infrastructure — start free, no setup.
Is Claude Code safe to use on my codebase?
It operates under a permission system that asks before risky actions, and its search is local (no code index shipped elsewhere by default; enterprise deployments run via Bedrock/Vertex). Like any agent, the practical risks are unreviewed output and over-broad permissions — keep the review gate.
What are dynamic workflows in Claude Code?
Shipped May 28, 2026 (v2.1.154): Claude writes an orchestration script that coordinates up to 16 concurrent subagents (1,000 per run) with deterministic loops and verification steps — built for work too big for one context window.
📚 Further Reading
- Anthropic & Claude: The Complete History — the company behind the tool
- What Is OpenAI Codex? The Complete History — the rival lineage
- Best Claude Code Skills (Tested) and Claude Skills, Explained
- Claude Code vs OpenClaw · Claude Code vs n8n · Claude Code vs Cursor vs Taskade Genesis
- What Is an Agent Harness? · Agentic Workflows Explained · The Execution Layer Thesis
- What Is Agentic Engineering? — Karpathy's framing and the discipline it became
- Best Claude Code Alternatives · Free Claude Code Alternative