AI & Technology
Claude Mods bring context, tool calls and next steps into the interface
Boris Cherny introduced Mods as a way to change Claude Code’s interface and behavior: users can add information, intervene before tools run and share their modifications as plugins.
An ordinary skill primarily supplies instructions to the model, while external tools supply capabilities. Mods run JavaScript or TypeScript handlers inside Claude Code. When a prompt is submitted, a tool is about to run or the interface is drawn, a handler can observe, modify or take over the event. That allows both new panels and changes to how an operation proceeds.
The official blast-radius example pauses commands such as file deletion or force pushes, shows their expected impact and offers buttons to proceed or cancel. token-weather displays context-window usage above the input: how much of the information the model can accommodate has been used. replay-theater adds /replay to step through the previous turn’s file edits.
Thariq’s next-steps example suggests skills and commands to use next. ClaudeDevs’ You should Know highlights information that might be overlooked in output. These examples address what to do, what to notice and what to inspect before acting, placing reminders inside the workflow.
Users can describe a modification to Claude and have it create a Mod, or install an existing plugin. The documentation supports interface extensions in the terminal and the Code tab of Claude Desktop; support differs across other environments. Mods execute code with the user’s permissions, making their authors and sources relevant to installation choices. This report describes published capabilities and examples, not our own product testing.