Anthropic's Claude Code team just cracked open a new extension surface, and it didn't arrive with a blog post or a press release — it arrived as a GitHub issue. On September 14, 2026, Boris Cherny, part of the Claude Code team at Anthropic, posted on X: "Claude Mods are landing now," linking to GitHub issue anthropics/claude-code#91870. Within hours, community members had already built and shared working Claude Code Mods, and the story was trending across Reddit and X under headlines like "Claude Code Launches Mods for Custom AI Coding Tools."
If you've followed explainx.ai's coverage of Agent Skills, MCP servers, hooks, and subagents, you already know Claude Code has been steadily growing extension points all year. Mods are the newest one — and the earliest, least-documented one yet.
TL;DR
| Question | Answer |
|---|---|
| What is it? | A new community modding/extension layer for Claude Code |
| Who announced it? | Boris Cherny (Anthropic, Claude Code team) on X, September 14, 2026 |
| Where's the official source? | GitHub issue anthropics/claude-code#91870 — no separate docs blog post |
| What's been built already? | A playable Tetris game, "Mindful Claude" (breathing exercises for HRV training), a CI status panel via RWX |
| How mature is it? | Early — no formal SDK docs, rolling community demos in a single GitHub thread |
| How is it different from skills/MCP/hooks/subagents? | Mods extend the session/interface surface, not the model's own tool-calling or invocation logic |
| Is there a registry or marketplace yet? | Not announced — contrast with the existing Claude plugin directory |
What Boris Cherny actually said
The announcement was terse by design — a single line, "Claude Mods are landing now," pointing at a GitHub issue rather than a documentation page. That choice is itself informative: Anthropic has, at various points in 2026, shipped skills, plugin bundles, and permission-mode changes with full write-ups. Landing mods through an open GitHub issue instead suggests Anthropic is treating this less like a finished product launch and more like a live, public beta — coordinating directly with the community members already building on it, in the open, before locking down an SDK.
That issue thread, anthropics/claude-code#91870, is doing double duty as both the changelog and the demo reel. It's where the Tetris game, Mindful Claude, and the RWX CI panel all got their first public mentions — not a press kit, not a docs site.
The first mods: what people have actually built
Three mods surfaced in the opening hours, and they're a useful signal of what this extension point is actually for — not because any one of them is a killer app, but because of how different they are from each other.
A playable Tetris game inside Claude. A community member built a fully playable Tetris implementation that runs directly inside a Claude Code session, referenced in the GitHub issue thread. It's a proof-of-concept in the oldest sense — the kind of "look what's now possible" demo that accompanies almost every new extension surface (compare it to the first VS Code extensions, or the first working demos on any plugin API). It tells you mods can render an interactive UI inside the session, which none of Claude Code's existing extension points — skills, MCP servers, hooks — are built to do.
Mindful Claude, by @halluton. This is the more conceptually interesting one. Mindful Claude has the user do breathing exercises while Claude is thinking — framed explicitly as a focus tool and for HRV (heart rate variability) training, instead of doomscrolling during the wait. It repurposes Claude Code's "thinking" latency — normally dead time for the human — into a structured, screen-adjacent wellness moment. That's a genuinely novel idea for a coding tool: using the agent's own processing delay as the trigger for something happening on the human side of the interaction, not the model side.
A CI status panel via RWX. A third community member built a mod that surfaces CI status from RWX (@rwx) directly inside a Claude Code session, and noted on X that it took roughly 20 minutes to put together. That's the practical, workflow-integration end of the spectrum — closer to what a developer would actually reach for day to day, and a useful data point on how low the barrier to entry looks for a straightforward mod.
Three mods, three different jobs: a game, a wellness ritual, and a CI dashboard. That range — rather than any single flagship use case — is the real early signal. It suggests mods are less a narrow feature for one workflow and more a general-purpose surface for wiring anything into the Claude Code session view.
How mods differ from skills, MCP servers, hooks, and subagents
explainx.ai has covered Claude Code's extensibility surfaces in depth — see the full comparison in Claude.md vs Skill.md vs MCP: the modern agent stack and skills vs hooks vs prompts: when to use each. Mods are new enough that Anthropic hasn't published a formal spec distinguishing them from those surfaces, but the early examples make the shape reasonably clear:
| Surface | What it extends | Who/what invokes it | Example |
|---|---|---|---|
| Agent Skills | The model's own capability set | The model, during reasoning | A packaged workflow for writing a specific kind of doc |
| MCP servers | External tools and data the model can call | The model, via tool calls | Connecting Claude to a database or SaaS API |
| Hooks | Lifecycle events in a session | The CLI runtime, at defined trigger points | Running a linter before every file write |
| Subagents | Task delegation to a separate agent context | The primary agent, when it delegates | Spawning a research subagent for a subtask |
| Mods | The session/interface surface itself | The person using Claude Code, as an add-on to what they see and interact with | A Tetris board, a breathing-exercise timer, a CI panel |
The distinguishing feature is that surface. Skills, MCP servers, and hooks all extend what the model can do or know. Mods, at least in every example public so far, extend what the human sees and does during a session — rendering something on screen, or coordinating a real-world activity around the session's own timing. That's a different axis of extensibility than anything Claude Code has shipped before, and it's the reason this feels closer to a VS Code extension marketplace than to another MCP server registry.
Why this looks like a platform moment, not a feature drop
Editors have a well-worn playbook here. VS Code went from a text editor to a platform the moment it exposed a stable extension API and let a community build on it — themes, linters, debuggers, entire language servers, none of which Microsoft had to write itself. CLIs have followed the same arc more recently: Claude Code's own plugin directory already crossed 127 listed plugins by mid-2026, and the claude plugin eval tooling that shipped in September exists precisely because a plugin ecosystem had grown large enough to need a way to measure whether a given plugin actually helps.
Mods look like the next rung on that same ladder — not a replacement for skills or MCP servers, but a new category the existing surfaces don't cover: the interactive, visual, session-level layer. If skills gave the model new capabilities and MCP servers gave it new tools, mods appear to give the session itself new surfaces — closer to what a browser extension does to a web page than what an MCP server does to a model's toolset.
Honest limitations: this is early, not a finished ecosystem
It's worth being direct about the maturity level here, because the framing in some social posts oversells it. As of September 15, 2026:
- There is no dedicated Anthropic documentation site or blog post for mods — the GitHub issue is the only official source, and issues are not a stable API reference.
- There's no published SDK, mod manifest format, or packaging spec that explainx.ai could find. Every known mod so far is a bespoke community build, not built against a documented interface.
- There's no mod marketplace or directory yet, unlike the existing Claude plugin directory that already lists dozens of vetted, one-click-install plugins.
- Security and permission implications are unclear. A mod that renders arbitrary UI inside a coding session, or coordinates real-world timing, raises the same trust questions explainx.ai has flagged for plugin permission modes generally — worth watching closely as more mods appear before installing anything from an unvetted source.
- The three known mods are all individually built demos, not a curated or reviewed set. Treat "Claude Mods are landing now" as the start of a rollout, not a completed feature.
None of that is a knock on the idea — most durable extension ecosystems (VS Code's included) started exactly this way, with a handful of enthusiast-built demos in an issue thread or forum before official tooling caught up. But readers evaluating whether to build on this today should go in expecting to reverse-engineer conventions from the GitHub thread, not follow a stable spec.
What this means if you want to build a Claude Code mod
- Start with the GitHub issue. anthropics/claude-code#91870 is currently the only place to see what's expected of a mod, how Anthropic is responding to community submissions, and whether any packaging conventions are emerging from the discussion.
- Study the three known examples for pattern, not code. Mindful Claude, the Tetris mod, and the RWX CI panel each show a different job — a game, a wellness loop, and a status dashboard — so look at what each one hooks into (rendering surface, session timing, external status data) rather than assuming one canonical mod shape exists yet.
- Keep your existing extensibility choices in place. If your problem is "the model needs a new capability," that's still a skill; if it's "the model needs to call an external tool," that's still MCP; if it's "run something at a lifecycle event," that's still a hook. Reach for a mod specifically when what you're building lives in the interactive session surface itself.
- Expect churn. Without a published spec, early mods built against undocumented internals are more likely to break as Anthropic formalizes the interface. Treat anything you build now as a prototype, not production tooling.
- Watch for a formal SDK and marketplace announcement. The jump from "GitHub issue with demos" to "documented API with a directory" is exactly the pattern Claude Code's own plugin ecosystem followed earlier in 2026 — expect a similar arc here if community interest holds.
What to watch next
- Whether Anthropic publishes a formal mods SDK, manifest format, or documentation page beyond the GitHub issue.
- Whether a mods directory or marketplace appears alongside the existing Claude plugin directory.
- How Anthropic addresses permissions and trust for mods that render UI or coordinate real-world activity, given the precedent set by Claude Code's permission modes for other extension types.
- Whether more community mods appear in anthropics/claude-code#91870 in the coming days, and what categories they cluster into beyond games, wellness, and CI integration.
Related reading
- What are Agent Skills? A complete guide
- What is MCP (Model Context Protocol)?
- Claude Code function hooks: the ant-apply CLI
- Claude Code subagents: multi-agent workflows
- Claude.md vs Skill.md vs MCP: the modern agent stack
- Skills vs hooks vs prompts: when to use each
- Top 25 Claude plugins in 2026
- claude plugin eval: measuring whether a plugin helps
- Claude Code permission modes explained
Primary sources: Boris Cherny (@bcherny) on X, September 14, 2026 · GitHub issue anthropics/claude-code#91870 · Mindful Claude by @halluton
This post reflects the Claude Code Mods announcement and community activity as of September 15, 2026. There is no formal Anthropic documentation for mods at the time of writing — the GitHub issue is the only official source, and packaging conventions, an SDK, and a marketplace may all change or appear as Anthropic formalizes the feature.