“No reason why everyone should have an identical Claude experience”: Anthropic’s mods let you change Claude Code’s look and behavior
The New Stack

“No reason why everyone should have an identical Claude experience”: Anthropic’s mods let you change Claude Code’s look and behavior

Existing Customization Options

Developers have long been able to customize Claude Code to their preferences, via settings, persistent instructions in CLAUDE.md, hooks, and MCP servers, alongside tweaks such as status lines and output styles. Those controls can shape the instructions Claude follows, its permissions, the tools it can use, and more - but they can’t change Claude Code’s own features or the rest of its interface.

Introducing Mods

Now, however, Anthropic is giving developers much deeper control of Claude Code via mods, which are small JavaScript or TypeScript functions that hook into events inside Claude Code. A mod can:

  • Rewrite a prompt before it reaches the model
  • Block or rewrite a tool call
  • Handle permission requests
  • Replace parts of Claude Code’s interface
  • Add entirely new functionality

“Each person works differently, so there’s no reason why everyone should have an identical Claude experience.”

Changing How Claude Code Looks and Behaves

Taking to X on Thursday, Claude Code creator Boris Cherny describes mods as a way for developers to reshape Claude’s appearance and behavior via a simple prompt, with the ability to package those customizations as plugins that other users can install. “Each person works differently, so there’s no reason why everyone should have an identical Claude experience,” Cherny writes.

That can include changing what Claude Code displays while it’s working. For example, a mod might surface live information such as:

  • The number of tool calls Claude has made
  • How long it has been running
  • How many tokens it has consumed

then present a summary once the task is complete.

Users were already experimenting with more specialized uses within hours of the announcement. One software developer built a mod for passing credentials to Claude without leaving the underlying secret in the conversation history.

How Mods Work

Mods have actually been in the works publicly for at least a month already. Anthropic first floated the idea on GitHub on September 3 under the more technical name “function hooks,” asking developers for feedback on an API that would let JavaScript and TypeScript functions intercept events inside Claude Code. Six days later, the company said it planned to ship the feature imminently under a rebranded “Claude Mods,” while retaining function hooks as the underlying mechanism.

Mods are now enabled by default in Claude Code 2.1.287 and later. Because a mod’s code stays active throughout a session, it can remember information between events and interact with Claude Code as things happen. That makes it possible to build interface elements that update live, launch processes, add commands, or expose new tools to the model.

Anthropic says that it’s already using mods for features including AGENTS.md support and the /diff pane, and has published their source in the Claude Code repository. “That makes mods a way to fit Claude Code to how you work.”

Example: Token Weather Mod

In a technical blog post accompanying the launch, Addy Osmani, a member of technical staff at Anthropic, acknowledges that developers could already customize Claude Code through various mechanisms. However, he says that mods give them control over Claude Code’s own behavior and interface, with modules that respond to events during a session and can alter or replace what Claude Code does. “That makes mods a way to fit Claude Code to how you work,” Osmani writes.

In one example, Osmani walks through an approximately 80‑line Mod called Token Weather, which tracks how much of Claude’s context window has been consumed and displays the result in a band above the prompt. As Claude reads more files, the display moves from:

  • “Clear” at 18 % of a 200,000‑token window
  • “Showers” at 67 %
  • “Storm” at 81 %

while also showing recent usage and how many tokens the latest turn added.

// Token Weather mod (≈80 lines)
function tokenWeatherMod(event) {
  // implementation details...
}

Security Considerations

Given that mods are distributed as plugins, developers can publish them through the same plugin mechanism, including from repositories on GitHub. That does, however, introduce a security consideration: mod code executes locally with access through Claude Code to the developer’s machine, so Anthropic recommends inspecting the source and installing only code from trusted publishers.

For teams, however, mods inherit Claude Code’s existing plugin controls, while Team and Enterprise users and machines with managed settings load Anthropic’s sec‑default guard ahead of user‑installed mods. By default, that prevents those mods from overriding permission‑deny rules; outside those guarded environments, mods can override some permission decisions.

Availability

Mods are available now in the Claude Code CLI and desktop app, and can be installed or shared through plugin marketplaces, including GitHub repositories.

Read on The New Stack ↗ ← Back to News

Comments

No comments yet. Start the discussion.