Claude Code Timeline: Release Date and Major Updates (2026)

Claude Code is Anthropic’s AI coding agent for working inside your project. Anthropic released it in research preview on February 24, 2025, and made it generally available on May 22, 2025.

The following timeline records the public milestones that changed how you can use Claude Code, including its terminal release, IDE support, project configuration, cloud and remote sessions, automation, and agent coordination.

It uses the date Anthropic announced or released each enduring capability, rather than every numbered changelog entry.

Note that Claude Code has a separate product history from the Claude models that power it and from Anthropic’s other Claude apps. This page includes a model release only when it changed Claude Code itself. For the wider model history, see the Claude Timeline.

Last updated: July 20, 2026.

Latest Claude Code update

Auto Mode became generally available on July 10, 2026, after its March research preview. It routes tool calls through a safety classifier before they run, so your session can continue through many ordinary actions without stopping for every approval.

Claude Code timeline at a glance

2024: MCP creates the integration foundation

November 25, 2024: Anthropic announces MCP

Model Context Protocol, usually called MCP, was announced as an open standard for connecting AI applications to tools and data sources. Claude Code had not launched yet, but MCP later became one of its main extension paths. You can use MCP to give a coding session access to a ticket, an error report, a database, a design file, or a private service without pasting all of that context into a prompt.

Explore Model Context Protocol servers for development and agent workflows.

2025: from terminal preview to a broader coding product

February 24, 2025: Claude Code enters research preview

Anthropic introduced Claude Code as a command-line tool for agentic coding on the same day it released Claude 3.7 Sonnet. The preview could inspect a codebase, edit files, run commands and tests, use Git, and complete tasks through a terminal session. The initial framing mattered: Claude Code was built to act inside a real development environment, not to produce isolated snippets in a chat window.

May 22, 2025: general availability and Claude 4

On May 22, Anthropic moved Claude Code out of research preview. The same announcement introduced Claude Opus 4 and Claude Sonnet 4, two models designed for difficult coding, reasoning, and agent work. Anthropic also announced native integrations for Visual Studio Code and JetBrains IDEs, plus GitHub Actions support for background tasks. From this point, you could use Claude Code beyond a terminal-only workflow.

June 18, 2025: remote MCP servers arrive

Remote MCP support let Claude Code connect to hosted servers through a URL and OAuth authentication. You no longer had to run every integration locally. Connect tools such as Linear or Sentry when you need issue details, project context, and error reports in the same session that edits the repository. Keep local MCP servers for tools that must run only on your machine.

June 30, 2025: Hooks become available

Hooks added event-driven control around Claude Code actions. Your project can run a command, a prompt, or another check when a session starts, before a tool runs, after a tool completes, or when Claude stops. Use them for project habits that should not depend on the model remembering an instruction, such as formatting after edits, checking a command against a policy, recording a session summary, or blocking an unsafe operation.

July 24 to July 30, 2025: custom Subagents and agent controls

The July releases opened a more explicit delegation model. You could define Custom Subagents through /agents, then call one for a focused task such as code review, investigation, testing, or documentation. Subsequent releases added SessionStart Hooks, direct mentions for custom agents, and model selection for agents. Keep the main session responsible for the task while an isolated agent explores part of the codebase and returns a summary.

August 5 and August 20, 2025: Opus 4.1 and business controls

Claude Opus 4.1 arrived on August 5 with an emphasis on coding precision and agent tasks. Two weeks later, Anthropic announced Claude Code access and administration for Team and Enterprise plans. If you manage a workspace, you could assign premium seats that included Claude Code and apply administrative controls. Claude Code then became part of the same subscription and governance decisions as the broader Claude product.

September 29, 2025: Claude Sonnet 4.5

Claude Sonnet 4.5 became a new model option for agents, coding, and computer use. It belongs in this timeline because a model release changes the practical choice you make inside a Claude Code session. The model does not replace your tools, project instructions, permissions, or integrations. It changes the reasoning and coding capability that works through them.

October 20, 2025: Claude Code on the web

Claude Code on the web entered research preview for Pro and Max users, with a later expansion to eligible Team and Enterprise users. After you connect a GitHub repository, it runs tasks on Anthropic-managed cloud infrastructure. Each task receives an isolated environment, can continue after you close the browser, and can create a pull request for review. Choose web sessions for work that can proceed with less continuous steering than a local terminal session.

October 27 and October 31, 2025: Plan Mode and Plugins

The October 27 release gave Plan Mode a dedicated Plan subagent. In Plan Mode, you can inspect a repository and ask for an approach without editing source files or running commands that change the project. Four days later, Anthropic announced Plugins and plugin marketplaces. A plugin can package commands, agents, Skills, Hooks, MCP servers, and related configuration so you can share a tested setup across projects or with colleagues.

November and December 2025: cloud handoff, Opus 4.5, and Slack

November releases expanded the handoff between local and cloud work. You could send background work to the web, and custom agents gained more configuration options. Claude Opus 4.5 followed on November 24 for demanding coding and agent tasks. On December 8, Claude Code in Slack entered research preview. Mention @Claude in a Slack channel to send the surrounding discussion into a Claude Code web session, then receive progress updates and a pull request link in the same thread.

2026: multi-agent work, remote sessions, and automation

February 5, 2026: Claude Opus 4.6 and agent teams

Claude Opus 4.6 added a new high-capability model for planning, code review, debugging, and longer tasks. The release also introduced agent teams in research preview. Use agent teams when you need several independent Claude Code sessions to work on related tasks at the same time. They can share work through the team structure and communicate beyond a single parent conversation.

February 20, 2026: desktop review tools and Claude Code Security

Claude Code Desktop gained tools for previewing a running app, reviewing pull requests, responding to CI failures, and moving a session between Desktop, web, mobile, and CLI. That same day, Anthropic announced Claude Code Security as a limited research preview for Team and Enterprise customers. It scans codebases for vulnerabilities and proposes patches for your review. Treat it as a specialized product surface, not a replacement for ordinary code review or security testing.

February 25 to March 19, 2026: Remote Control, memory, and Channels

Remote Control expanded to more users in late February. It connects your local Claude Code session to claude.ai/code or the Claude mobile app while execution and filesystem access remain on your machine. Claude Code also added auto memory for useful session context and later added names for Remote Control sessions. On March 19, the --channels preview opened a different path: selected MCP servers could push events into an active session.

March 24 and July 10, 2026: Auto Mode moves from preview to general availability

Auto Mode began as a Team-plan research preview on March 24. It uses a classifier to examine tool calls before they run. Routine actions can proceed without a separate approval, while risky actions are blocked or returned to you for a decision. Anthropic later updated the announcement to say Auto Mode was generally available on July 10. Your access can still depend on a plan, provider, administrator setting, or workspace policy, so check your Claude Code settings before relying on it.

April 14, 2026: a redesigned Desktop app and Routines

Anthropic released a new Desktop workspace with a sidebar for sessions, a flexible layout, an integrated terminal, and a file editor. It arrived on the same day as Routines, a research-preview feature for repeatable cloud automations. A Routine can run on a schedule, after an API call, or in response to a GitHub event. It keeps its own prompt, repository, and connected tools. Use it when you want managed automation for issue triage, documentation checks, or release verification.

May 11 to June 2, 2026: Agent View, Remote Control in VS Code, and dynamic workflows

Agent View entered research preview on May 11. It lists Claude Code sessions that are running, blocked, or finished, and /goal lets you define a completion condition for persistent work. On May 13, the VS Code extension gained /remote-control. Dynamic workflows arrived in research preview on June 2. Claude Code can create a task-specific harness that splits work among agents, checks results, and combines the output. Use it for complex work where one fixed prompt or one linear agent loop is not enough.

May 28 to June 30, 2026: new models for Claude Code

Claude Opus 4.8 arrived on May 28 for coding and longer agent tasks. Anthropic announced Claude Fable 5 and Claude Mythos 5 on June 9 with different availability and safety policies. Claude Sonnet 5 followed on June 30 for coding, tool use, agents, and professional work. Because model names and access can change quickly, focus on which model your account, provider, and task can use. The product’s extension layer remains separate from that choice.

How Claude Code customization fits together

CLAUDE.md is your project context file. Claude Code reads it at the start of a session. Put repository commands, architecture notes, coding conventions, test requirements, and review rules there. A root file can set broad project guidance, while files in subdirectories can carry local instructions for a package or service. Use it for context that should apply repeatedly.

Hooks respond to events. Use them when a command or policy must run predictably, such as formatting after a write, checking a changed file, or preventing a prohibited action. A Hook does not depend on Claude choosing to follow a paragraph of guidance. That makes it suitable for safeguards and mechanical project tasks.

MCP servers connect Claude Code to external systems. A local server can expose a tool on your machine. A remote server can connect through a hosted URL and OAuth. Use MCP when your task requires issue data, logs, design context, internal documents, or a company service that Claude Code cannot reach through the repository alone.

Skills package reusable instructions and workflows. You can invoke a Skill directly, or Claude can load one when its description matches the task. Choose a Skill instead of a large global instruction file when a workflow is specific to code review, release preparation, a framework, or a deployment process.

See the Best Agent Skills guide for examples beyond Claude Code.

Plugins bundle capabilities for distribution. A plugin can include Skills, Subagents, Hooks, MCP configuration, and commands. Use one to share a tested setup without asking every developer to recreate it by hand. Marketplaces give your project or organization a place to discover and manage those packages.

Subagents and agent teams divide work. A Subagent has its own context and returns a result to your main session. Agent teams coordinate several independent sessions for work you can split, such as a large codebase review, separate investigations, or competing implementation proposals. Set clear task boundaries so agents do not duplicate work or touch the same files.

Plan Mode is the safer place to inspect a repository and agree on an approach before edits begin. It can read files and explain a proposed change, but it does not edit the project. Use it when a task is ambiguous, has a broad blast radius, or needs a design decision before implementation.

Model changes that affected Claude Code

Claude Code launched with Claude 3.7 Sonnet. That model introduced Anthropic’s hybrid reasoning approach, with a regular response path and extended thinking for harder work. Your early product experience was therefore tied closely to a model intended for coding and multi-step problem solving. The terminal agent supplied the repository access, tools, and approval flow that put that model capability to work in a development environment.

Claude Opus 4 and Claude Sonnet 4 arrived when Claude Code became generally available in May 2025. Opus was positioned for the hardest tasks, while Sonnet provided a more balanced option for everyday coding and agent work. Opus 4.1, Sonnet 4.5, and Opus 4.5 later refined those choices. A model release can improve planning or code editing, but your repository context and tool permissions still determine what the agent can inspect and change.

The 2026 releases pushed the model discussion further toward long-running work. Opus 4.6 arrived with stronger code review and debugging behavior, then Opus 4.8 followed in May. Anthropic announced Fable 5 and Mythos 5 in June with separate availability and safety policies. Sonnet 5 arrived later that month.

If you need the complete model sequence, use the Claude Timeline.

There is no single permanent answer to which model is best in Claude Code. Your available choices depend on a subscription, an API account, or a cloud provider. The right option also depends on whether you need a short edit, a repository investigation, a code review, or a task that will run with several agents. Use the model selector and account documentation for the live choice. Treat an older timeline entry as history, not a fixed recommendation.

Commands and configuration changes that shaped the workflow

Claude Code started with a simple pattern: open your project directory and run claude. The product then gained commands that support longer or more structured work. Use /init to create a starting CLAUDE.md file, /agents to manage Custom Subagents, /mcp to manage connections and authentication, and /plugin to discover, install, validate, and update Plugins. Each command belongs to a different part of the product, not a separate coding agent.

Permission controls changed as Claude Code moved beyond a short supervised terminal session. Plan Mode gives you a read-only path to investigate first. Accept Edits reduces file-edit prompts while leaving other actions subject to approval. Auto Mode adds classifier-based screening for eligible accounts and environments. The older --dangerously-skip-permissions option does not provide the same safeguards. If your project has production credentials or destructive scripts, define permissions and Hooks carefully before you use less interactive modes.

Remote work introduced another group of commands. /remote-control and its CLI forms connect your local session to a browser or mobile device. /schedule maps repeatable work to Routines where the feature is available. /goal gives a session a completion condition, while Agent View shows work that is in progress or waiting for input. Use these features when you need monitoring over time, but continue to review diffs, test results, and pull requests.

Configuration also became more layered. Keep shared instructions in CLAUDE.md, personal settings in your user directory, and local exceptions in ignored settings files. Managed settings can apply organization rules. Plugins can distribute a common package of Skills, Hooks, agents, and MCP configuration.

For syntax and a command-by-command reference, use the Claude Code Commands Cheat Sheet.

What changed over time

Claude Code began as a terminal agent for a development task in a local repository. Its first year added the parts you need for repeated use: a model upgrade path, IDE views, remote MCP connections, lifecycle Hooks, project instructions, Custom Subagents, enterprise controls, and a way to package configuration through Plugins.

The later releases changed the shape of your session. You can now move work between terminal, editor, Desktop, browser, phone, and Slack. Some tasks run in an Anthropic-managed environment. Others stay on your local computer but can be controlled remotely. Routines, Agent View, Auto Mode, agent teams, and dynamic workflows support work that takes longer than one prompt and needs coordination, monitoring, or a defined stopping point.

FAQs

When was Claude Code released?

Anthropic introduced Claude Code on February 24, 2025, as a limited research preview with Claude 3.7 Sonnet. It became generally available on May 22, 2025.

Is Claude Code free?

No. The free Claude.ai plan does not include Claude Code. To use it regularly, you need a paid Claude plan, such as Pro, Max, Team, or Enterprise, or a billed developer account through Anthropic Console, Amazon Bedrock, Google Vertex AI, or Microsoft Foundry. Subscription use counts toward your plan’s usage limits. API and cloud-provider use is billed by tokens.

Which Claude model should I use with Claude Code?

Start with default unless you have a reason to override it. It selects Anthropic’s recommended model for your account. For everyday implementation, use sonnet. Choose opus for difficult debugging, architecture decisions, code review, or a high-risk multi-file change. Choose opusplan when you want Opus to make the plan and Sonnet to carry it out. Use haiku for simple, fast, lower-cost tasks. Run /model to switch during a session.

What is the difference between Claude Code on the web and Remote Control?

Claude Code on the web runs a task in Anthropic-managed cloud infrastructure. Remote Control lets your browser or mobile device steer a Claude Code session that is still running on your own machine. Use Remote Control when local files, tools, or MCP servers are part of the task.

What should go in CLAUDE.md?

Put stable project guidance in CLAUDE.md: how to run tests, coding conventions, architecture decisions, preferred libraries, repository rules, and review requirements. Keep reusable task workflows in Skills, automatic checks in Hooks, and external-service access in MCP configuration.

Are Claude Code Plugins the same as Skills?

No. A Skill is a reusable set of instructions or workflow guidance. A Plugin is a distributable package that can include Skills alongside commands, Subagents, Hooks, MCP servers, and other Claude Code components.

What is Plan Mode in Claude Code?

Plan Mode is a read-only working mode for investigating a codebase and proposing a change before implementation. Claude Code can inspect files and explain an approach, but it does not edit files or run commands that change the project. Use it when you need to review the plan before granting execution access.

More Related Resources

• 7 Best CLI AI Coding Agents
• Free AI Tools for Developers
• Most Popular Agent Skills on GitHub for Coding Agents