Claude Code Mods let you change the interface and how it works

Anthropic introduced Claude Code Mods on October 1. Developers can add interface elements, change how tools run and replace assistant features with small TypeScript modules. Mods work in the Claude Code terminal and desktop app.

With mods, a team can adapt its coding session without waiting for an Anthropic update. The official announcement explains how to install and share those modifications. The cover illustration is also by Anthropic.

Three demos that show what changes

The Anthropic tutorial presents three examples. Select one and play the recording; switch to full screen to read the terminal more closely.

Official demosClaude Code · Terminal

Token Weather displays context window usage: how much space the conversation takes up in the material Claude uses to answer. The demo moves from 18% to 67% to 81%. It lets you follow a growing session; those percentages do not measure API spending.

Blast Radius pauses a deletion command and lists the files it would affect before asking for confirmation. Its text-based classification can miss commands hidden in aliases or scripts. Permission rules remain necessary.

Replay Theater lets you step through a turn’s file edits and review their diffs. The view helps you inspect the sequence of changes. The example shown does not provide an undo function.

The recordings demonstrate example features. When evaluating a mod for your project, check which actions it intercepts and which it lets through.

What a Claude Code mod does

The mods documentation explains that Claude Code emits events when it receives a prompt, calls a tool or draws the interface. A mod can act on those events: observe what happens, modify it or respond in its place.

For example, a mod can rewrite a prompt before it reaches the model, block a call or add a pane. Anthropic also lets you ask Claude to build the mod and reload it during a session. The tutorial requires Claude Code 2.1.287 or later and notes that the API can change between releases.

Some Claude Code features already use this structure. The /diff pane, which lets you review file differences, is now a mod that you can disable or replace. A team building its own review view should check which changes it shows before using it to approve work.

Mods, plugins and MCP: what each does

Mods ship inside plugins. MCP connects the assistant to external tools and data, as described in the Claude Code documentation.

Swipe the table to see all columns.

HeyMark’s connection to Claude uses MCP to let the assistant read your accounts’ posts and metrics after you authorize access. You can follow that guide with the current connector, without installing a mod. HeyMark’s integration with these new mods has not been tested yet.

What to check before installing a mod

Anthropic warns that mods have the same access to your machine as Claude Code. Review the author, code and permissions before installing one, especially if it handles tool approvals.

We suggest starting with a test copy of your project, a small task and an outcome you can check. Review the file changes and test both an action the mod should allow and one it should block. If you share it with a team, document those limits alongside the installation instructions.

You can explore the Claude Developers thread on X and the sample mods’ source code to see how they are built.