Field noteNov 15, 20265 min read1 source

Draw in the interface with a mod

In one minute

Claude Code’s mod interface lets plugins add panels and transcript rows, or change parts of the interface Claude Code already renders. The documentation’s working example combines tabs, buttons, redraws and state saved between sessions, giving builders a concrete pattern for extending a coding-agent interface without replacing the whole application.

What happened

Anthropic’s Claude Code documentation describes how a mod can draw its own interface or alter one Claude Code already draws. Each drawable location is called a render site. The documentation names panes, a band above the prompt, transcript rows, messages, tool-call rows, status elements and the spinner among the possible sites. A ui.render hook runs when Claude Code is about to draw a site; the hook can return an element tree, modify the existing drawing, or pass the event onward unchanged.

The worked example builds a plugin named hello-tabs. Its manifest identifies the plugin and its version as 0.1.0, while hooks.json points to a JavaScript module. At session start, the mod registers a /hello-tabs command and reads a saved counter value from $.store. Running the command opens a pane. The pane contains two tab buttons; one tab displays a short message, while the other displays an “Add one” button and the counter. The button changes the count, requests a redraw, and saves the value. The guide says the count remains after Claude Code is restarted. It instructs readers to launch Claude Code with claude --plugin-dir ./hello-tabs to try the example.

The render cycle is the key implementation pattern: event handlers change state, call $.ui.invalidate('ui.render'), and Claude Code runs the render hook again to build the interface from the updated values. For existing interface elements, a mod can pass next a copy of the event with changed properties, return a custom tree instead, or call next(e) to preserve the standard drawing. The documentation’s spinner example adds a tool-call count to the existing spinner while retaining its animation.

The interface adapts to the surface. In a wide fullscreen terminal, a pane can sit beside the transcript; otherwise it appears above the prompt. The guide says a pane’s requested side-by-side width is capped at 45 percent of the terminal. In VS Code, the documented interface support begins with extension version 2.1.299; sessions that do not fetch feature flags need 2.1.304 or later. The extension handles pane sizing itself, does not provide button hotkeys, and truncates status lines at 200 characters or two rows and toasts at 500 characters. A separate transcript-row API, $.ui.place, requires Claude Code v2.1.314 or later.

What the archive adds

New Runtime’s earlier coverage of Claude Code’s privacy mod on November 6, 2026, described a specific mod published under Anthropic’s existing TypeScript mods offering. This documentation adds a practical interface-building guide rather than announcing a new mod or a change to that earlier event.

Trend signal

This does not yet fit a pattern New Runtime tracks. The guide documents a particular plugin interface and render lifecycle; it does not by itself establish a broader shift in how agent software is architected or integrated.

Why now

The guide gives builders a way to make Claude Code mods more than command wrappers: they can provide persistent panels, interactive controls and contextual status displays. That matters when a team has a repeatable workflow that benefits from a purpose-built surface inside its coding-agent session.

Why it matters

A custom interface can keep workflow state and controls close to the coding conversation. The example shows the basic ingredients: register a command, open a pane, render from state, redraw after interaction, and persist a value when it should survive a restart. That is a reusable structure for small tools such as task counters, review status or project-specific controls, although those use cases are examples rather than claims made by Anthropic.

The interface hooks also create choices about how much of Claude Code to replace. Passing a modified event to next preserves the standard element while changing a detail; returning a new tree replaces it. That distinction can help a mod remain legible alongside the host interface. Teams targeting both terminal and VS Code surfaces will need to account for layout, keyboard and text-limit differences instead of assuming that a terminal design transfers unchanged.

Limits and uncertainty

The documentation demonstrates an example and describes API behavior; it does not report adoption, reliability measurements, user outcomes or the maintenance cost of real mods. The example’s counter is intentionally simple and does not establish how more complex state should be synchronized across concurrent actions or shared among users. Surface-specific behavior also means builders should test their target Claude Code versions and interfaces directly. The guide states version thresholds for some capabilities, but this page alone does not establish that every documented behavior is available in every installation or deployment.

Skill to build now

Build a small mod that renders one piece of workflow state in a pane. Follow the documented cycle: register a command at session start, open the pane when the command runs, render from state in ui.render, and invalidate that render after a button changes the state. If the value should survive a restart, store it with $.store and load it when the session starts. Test the layout in the terminal width and editor surface your team actually uses.

Reader takeaway

Claude Code mods can add interactive interface surfaces as well as commands. The most reusable lesson in the guide is to treat rendering as a repeatable state-to-view cycle, then verify the different layout and input behaviors of each supported surface.

Evidence / sources

  1. 1code.claude.com/docs/en/plugins/mods/interface
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicClaudeExplore the claude topic hub.
  2. 02topicClaude CodeExplore the claude-code topic hub.
  3. 03topicAnthropicExplore the anthropic topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract