Getting started with Claude Code mods news update
. Getting started with Claude Code mods news update Why it matters for engineering teams What shipped and who is affected.
By Dillip Chowdary • Oct 02, 2026 • Source: HN Claude/Codex/Fable

At a glance
- Format
- JavaScript or TypeScript module inside a plugin folder
- Requires
- Claude Code 2.1.287 or later
- Manifest
- .claude-plugin/plugin.json
- Example
- Token Weather, a live context-window forecast
- Bands
- Clear at 18%, Showers at 67%, Storm at 81%
- Hooks
- chained like middleware, each passes to next()
In this post
01What shipped
Mods can rewrite or replace what Claude Code does, and can even draw custom UI. Each one is a small JavaScript or TypeScript module that runs inside your session and sees every event as it happens.
You can add a readout you check all the time, put a guard in front of the commands that make you nervous, or build a review view for how you like to read changes. This guide builds one mod from an empty folder, Token Weather, a live forecast of the context window drawn above the prompt.
02What improved
Then it tours two larger mods, Blast Radius and Replay Theater, to show what else the API can do. See the full write-up from HN Claude/Codex/Fable via the source link for quotes and complete context.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
03What you gain
TerminalDesktopFIG AToken Weather, Blast Radius and Replay Theater, one after another, in a terminal session Play videoFIG BPauseToken Weather's band as the context window fills: Clear at 18%, Showers at 67%, Storm at 81% Claude Code 2.1.287 or later. Each time Claude Code loads a mod, it writes the type declarations for your build into the mod's .claude-plugin/types/ folder, and those are the authority for your version.
04How to get it
HOW A MOD WORKS A mod is a Claude Code plugin whose behavior lives in a JavaScript or TypeScript module: The folder is a normal plugin, with a .claude-plugin/plugin.json manifest. Every hook has the same shape: CODEJavaScriptCopyon("tool.call", { tool: "Bash" }, async ($, e, next) => { // $ the mods API: ui, session, state, store, fs, process, clock, http, tool, command, model, ...
05What to watch next
// e this event's input, as plain data // next passes e to the other plugins and then to Claude Code's own behavior return next(e); }); Hooks form a chain, like middleware. See the full write-up from HN Claude/Codex/Fable via the source link for quotes and complete context.
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Introducing Clef: our open-source decision models, and new RL fine-tuning platform
Read →
Microsoft AI models are now available on AI Gateway
Read →
Better Call GPT – Plugin for Talking to Claude Code in Live
Read →
Hermes ChatGPT Extension – Your Hermes Agents Inside Codex/ChatGPT
Read →
Today's Tech Pulse briefing
Full briefing →
Advertisement