Anthropic shipped Claude Code mods in v2.1.287 (Oct 1, 2026) — in-process TypeScript event handlers that run inside the coding agent, not beside it. Mods can redraw the TUI/desktop UI, intercept and rewrite tool calls and prompts, pre-approve permission requests, read secrets from tool output, and spend the user's API budget. The first-party docs explicitly enumerate this trust surface and ship mitigations (plugin validation, --safe-mode, disableAllHooks, org admin limits, a protective sec-default mod on Team/Enterprise plans). ~204 hours post-launch, 16+ third-party mods exist but all are weakest-tier reception; the mix has drifted from UI toys toward middleware utilities (handoff-compact, xcodebuild rewrite, usage bands, spec review, guardrails 0.2.0), and established plugin authors (claude-dashboard, statusline-anywhere) plus one established OSS project (Repowise Lens, 7k stars) have migrated — yet no mod has real traction. The trust surface is now folk knowledge among casual Pro users, but no outside security voice has named the self-approving/secret/spend surface a supply-chain risk, leaving Scott's dated-receipts publishing window (Breach Doesn't Compose / Agent Provenance Stack) open and aging.
| source | object | author | score | comments |
|---|
| 🟠 reddit | You can now mod Claude Code: - Change how it behaves - Customize the UI - Swap in your own features Write one with a few lines of TypeScript, or have Claude build it for you. Mods ship inside plugins, so you install them with /plugin in the CLI or desktop app. ClaudeAI | GroovyMelodicBliss | 18 | 9 |
| 🟧 hn | Claude Code Mods: plugins may now modify deeper behaviorRetrieved article excerptOpen article · Retrieved 2026-10-01T20:35:58.918650+00:00 Mods
# Mods overview
Copy pageCopy page
Add panes, commands, and tool call rules to Claude Code with a mod. See what a mod can do, how to make or install one, and where mods run.
Copy pageCopy page
A mod is a [plugin](https://code.claude.com/docs/en/plugins/overview) that changes how Claude Code looks and behaves. It’s made of JavaScript or TypeScript event handlers: Claude Code calls one when an event happens, such as a tool call, a submitted prompt, or a part of the interface being drawn, and the handler can watch the event, change it, or take it over. Use a mod to add a feature of your own to Claude Code, such as a pane that charts how full your context is after each request. For the files in a mod and a complete example, see [How a mod works](https://code.claude.com/docs/en/plugins/mods/overview#how-a-mod-works).
Claude Code’s existing [hooks](https://code.claude.com/docs/en/hooks) also run on events, as a shell command, HTTP request, or prompt you configure in a settings file. A mod’s handlers are functions that run inside Claude Code instead. Claude Code calls both kinds hooks: on these pages, “hook” means a mod’s handler, and the settings-file kind is a “settings hook”.
## [](https://code.claude.com/docs/en/plugins/mods/overview#what-a-mod-can-do) What a mod can do
Settings hooks, skills, status lines, and MCP servers work from outside Claude Code: each one runs a script, or gives Claude text or tools. A mod runs inside Claude Code, so it can do things they can’t:
- **Draw an interface you can use**: a pane beside the transcript or a band above the prompt, with tabs, buttons, and text fields. See [Draw in the interface](https://code.claude.com/docs/en/plugins/mods/interface).
- **Redraw Claude Code’s own interface**: replace or restyle parts Claude Code draws itself, such as a tool call’s row, the spinner, or the dialog Claude asks questions in. See [Change what Claude Code already draws](https://code.claude.com/docs/en/plugins/mods/interface#change-what-claude-code-already-draws).
- **Step into a tool call or a request**: for example, hold a tool call while you ask the user a question, answer it without running the tool, or send one request to a different model. See [Guard or change a tool call](https://code.claude.com/docs/en/plugins/mods/events#guard-or-change-a-tool-call) and [Follow a turn](https://code.claude.com/docs/en/plugins/mods/events#follow-a-turn).
- **Run your own code on a command**: a `/command` that runs your function at once, with no Claude turn, even while Claude is working. See [Add a command or a tool](https://code.claude.com/docs/en/plugins/mods/api#add-a-command-or-a-tool).
- **Share data between hooks**: a mod’s hooks share the variables in its file, so what one hook records, another can show. For example, one hook can count tool calls while another shows the count beside the spinner, or one can read each request’s token usage while another charts it in a pane. See [React to events](https://code.claude.com/docs/en/plugins/mods/events).
Mods work in the Claude Code CLI and in the Code tab of the Claude Desktop app. See [Where mods run](https://code.claude.com/docs/en/plugins/mods/overview#where-mods-run) to understand how they behave elsewhere, such as in the VS Code extension, `claude -p`, and cloud sessions. If a settings hook, a skill, or an MCP server already does what you need, [compare them](https://code.claude.com/docs/en/plugins/mods/overview#compare-mods-settings-hooks-skills-and-mcp-servers) before you write a mod. To manage mods for an organization, see [Manage mods for your organization](https://code.claude.com/docs/en/plugins/mods/admin).
## [](https://code.claude.com/docs/en/plugins/mods/overview#get-a-mod) Get a mod
You can start with a mod in one of three ways:
- **Use one you already have**: some of Claude Code’s own features are mods, such as `/diff`. See [Mods built into Claude Code](https://code.claude.com/docs/en/plugins/mods/overview#mods-built-into-claude-code).
- **Make one**: describe what you want in a Claude Code session, and Claude writes the mod. See [Ask Claude for a mod](https://code.claude.com/docs/en/plugins/mods/create#ask-claude-for-a-mod). To learn how a mod’s code works, [write one yourself](https://code.claude.com/docs/en/plugins/mods/create#write-a-mod-yourself).
- **Install one**: see [Install or update a mod](https://code.claude.com/docs/en/plugins/mods/overview#install-or-update-a-mod)
### [](https://code.claude.com/docs/en/plugins/mods/overview#install-or-update-a-mod) Install or update a mod
A mod is code that runs with your permissions. It can read and write your files, start processes, and make network requests. Install mods only from authors and marketplaces you trust. See [Decide whether to trust a mod](https://code.claude.com/docs/en/plugins/mods/overview#decide-whether-to-trust-a-mod).
A mod installs as a plugin, from a marketplace. Give the plugin’s name, an `@`, and the marketplace’s name. These examples install a plugin named `token-chart` from a marketplace named `your-org`:
- In a Claude Code session, run `/plugin install token-chart@your-org`.
- In your shell, run `claude plugin install token-chart@your-org`.
[Install plugins](https://code.claude.com/docs/en/plugins/install) covers marketplaces, scopes, the VS Code extension and the Desktop app, and [keeping plugins updated](https://code.claude.com/docs/en/plugins/install#keep-plugins-updated), all of which apply to a plugin that contains a mod without changes.
If you install or update a mod from your shell while a session is open, run `/reload-plugins` in that session to load it. Otherwise it loads the next time you start Claude Code.
## [](https://code.claude.com/docs/en/plugins/mods/overview#decide-whether-to-trust-a-mod) Decide whether to trust a mod
A mod is code that runs with your permissions, inside Claude Code. Install mods only from authors and [marketplaces you trust](https://code.claude.com/docs/en/plugins/security).
### [](https://code.claude.com/docs/en/plugins/mods/overview#what-a-mod-can-reach) What a mod can reach
A mod runs with your permissions, so before you install one, know what it has access to. Once it loads, a mod can:
- **Act on your machine as you**: read and write files anywhere your user account can, start programs, and make network requests
- **Read your secrets**: environment variables and settings files, including an API key you keep in either
- **See your session**: every prompt you send and every tool call Claude makes
- **Change your session**: rewrite a prompt or a tool call, submit a prompt as if you had typed it, or send a message to another of your sessions
- **Act without asking you**: approve a tool call before you’re asked
- **Spend your usage**: call a model on your plan or API key
A mod that approves tool calls can approve one that an `ask` rule would prompt for, or that one of your own `PreToolUse` hooks blocked. [Extend permissions with hooks](https://code.claude.com/docs/en/permissions#extend-permissions-with-hooks) lists what such a mod can approve, including when it can approve a call that a `deny` rule refuses.
A mod can restyle much of Claude Code’s interface, but not the permission prompt. It can’t change what a prompt shows you.
### [](https://code.claude.com/docs/en/plugins/mods/overview#list-what-a-mod-does-before-you-install-one) List what a mod does before you install one
Before you install a mod, you can list which events it hooks and what it asks Claude Code to do, such as read a file or make a network request, without running it. Get the plugin’s files first, for example by cloning its repository. Then, in your shell, run `claude plugin validate` on the plugin’s directory:
```
claude plugin validate ./some-mod
```
The `hooks:` and `calls:` lines in the output list the events the mod handles and what it asks Claude Code to do. [Review what a mod can do](https://code.claude.com/docs/en/plugins/mods/admin#review-what-a-mod-can-do) shows the output and which calls to look for.
## [](https://code.claude.com/docs/en/plugins/mods/overview#turn-mods-on-or-off) Turn mods on or off
Mods require Claude Code v2.1.287 or later, and they’re on by default. In your shell, run `claude --version` to check, and update Claude Code if yours is older.
To turn mods off, choose how many to stop, and for how long. To turn them back on, undo the same change:
- **One mod**: disable or uninstall its plugin from the [**Installed** tab in `/plugin`](https://code.claude.com/docs/en/plugins/install#manage-installed-plugins)
- **Every installed mod, for one session**: start Claude Code with [`--safe-mode`](https://code.claude.com/docs/en/cli-reference#cli-flags), which also leaves out your other customizations
- **Every mod you installed, in every session**: set [`"disableAllHooks": true`](https://code.claude.com/docs/en/settings-reference#disableallhooks) in `~/.claude/settings.json`. Your settings hooks and custom status line stop too. What your organization manages keeps running.
If you use Claude Code through an organization, an administrator can also limit which mods load. Administrators start at [Stop user-installed mods from loading](https://code.claude.com/docs/en/plugins/mods/admin#stop-user-installed-mods-from-loading).
To find out whether mods can load for you, see [Check whether mods can load](https://code.claude.com/docs/en/plugins/mods/troubleshoot#check-whether-mods-can-load).
If you set `CLAUDE_CODE_ENABLE_FUNCTION_HOOKS` during early access, remove it. Claude Code v2.1.287 and later ignores it, so setting it to `0` doesn’t keep mods off.
### [](https://code.claude.com/docs/en/plugins/mods/overview#see-which-mods-a-session-loaded) See which mods a session loaded
To see which mods a terminal session loaded, run `/plugin` at the Claude Code prompt. A dim line under the tabs gives the count and the names, such as `1 mod active · first-mod`. If a mod you installed isn’t named there, see [Find out why a mod does nothing](https://code.claude.com/docs/en/plugins/mods/troubleshoot#find-out-why-a-mod-does-nothing).
## [](https://code.claude.com/docs/en/plugins/mods/overview#how-a-mod-works) How a mod works
A mod is a [plugin](https://code.claude.com/docs/en/plugins/overview) whose code registers event handlers, called hooks. Claude Code runs a hook when its event happens, such as when Claude calls a tool or when the spinner is drawn. A small mod has three files:
```
first-mod/
├── .claude-plugin/
│ └── plugin.json
└── hooks/
├── hooks.json
└── register.js
```
- **`plugin.json`**: the plugin’s [manifest](https://code.claude.com/docs/en/plugins/manifest-reference)
- **`hooks.json`**: [points to your code file](https://code.claude.com/docs/en/plugins/mods/reference#files)
- **`register.js`**: [your code](https://code.claude.com/docs/en/plugins/mods/create#write-a-mod-yourself), called the hooks module. It tells Claude Code which events to run your functions on.
This is a complete `register.js`. It counts the tool calls Claude makes and shows the count beside the spinner while Claude works, as in `Thinking · tool calls: 3…`.
hooks/register.js
```
// The count, shared by the two hooks below
let calls = 0
// Claude Code calls this once when the mod loads
export function register(on) {
// Runs each time Claude is about to use a tool
on('tool.call', async ($, e, next) => {
calls += 1
// Ask Claude Code to draw the interface again, so the new count shows
$.ui.invalidate('ui.render')
// Let the tool run as usual
return next(e)
})
// Runs each time Claude Code draws the spinner
on('ui.render', { component: 'Spinner' }, async ($, e, next) => {
// Keep Claude Code's spinner, with the count added after its word
return next({ ...e, props: { ...e.props, suffix: ' · tool calls: ' + calls + '…' } })
})
}
```
The file registers two hooks, and both use the `calls` variable at the top:
- **The [`tool.call`](https://cod | rtuin | 3 | 0 |
| 🟧 hn | Getting started with Claude Code mods | mfiguiere | 3 | 0 |
| 🟧 echo.blog ⭐ | The origin is Anthropic's official docs page for "Mods", published with Claude Code v2.1.287. It defines the feature: "A mod is a plugin tha | Anthropic | — | — |
| 🟧 hn | Pi-autoresearch ported to Claude Code 1:1 using the new mods API | b--l | 2 | 0 |
| 🟧 hn | Show HN: What's Agent Doing – a Claude Code UI mod that explains each step | tzafrir | 2 | 0 |
| 🟧 hn | Multi-harness delegation Mod for Claude Code | FranciscoCarlos | 1 | 0 |
| 🟧 hn | Show HN: Status lines in the Claude desktop app | nastynate | 2 | 0 |
| 🟧 hn | Getting started with Claude Code mods | alwillis | 2 | 0 |
| 🟠 reddit | handoff-compact, a mod that does the handoff + /clear routine for you every time autocompact fires ClaudeAI | speciallight | 24 | 3 |
| 🟧 hn | Customize Claude Code with Mods in TypeScript | rbinv | 1 | 0 |
| 🟠 reddit | Built a Minecraft Skin for my Claude Code ClaudeAI | Funny_Language4830 | 0 | 3 |
| 🟠 reddit | Finally had some time to do something useful with mods ClaudeAI | cleverhoods | 1 | 2 |
| 🟧 hn | Show HN: Claude Mods – Minesweeper | cleverhoods | 1 | 0 |
| 🟠 reddit | I built a Claude Code mod that gives Claude your xcodebuild errors instead of the truncated build log ClaudeAI | Gary_BBGames | 2 | 1 |
| 🟠 reddit | Mods overview - Claude Code Docs ClaudeAI | TensorTrace | 3 | 1 |
| 🟠 reddit | What I learned building a Claude Code mod: a status band above the prompt ClaudeAI | Troepster | 1 | 1 |
| 🟠 reddit | I made a Mod that shows your 5h/weekly usage live, a reset forecast and context % above the prompt box, with optional auto compact and a manual compact button ClaudeAI | Antpocalypse_7 | 9 | 13 |
| 🟠 reddit | Built a Claude mod to help review spec and design documents ClaudeAI | revelationnow | 1 | 4 |
| 🟠 reddit | Did you know Claude Code has mods? They're awesome ClaudeAI | Necessary_Abroad6632 | 24 | 17 |
| 🟠 reddit | I counted how many times my hooks had to stop Claude in one week. 448 times in 76 sessions ClaudeAI | Ok-Motor-9812 | 67 | 45 |
| 🟠 reddit | Who managed to make mods work ? I get the same bug every time ClaudeAI | KlausWalz | 1 | 1 |
| 🟠 reddit | I built a live map for Claude Code that shows every file an edit touches ClaudeAI | Obvious_Gap_5768 | 1 | 1 |
| 🟠 reddit | Claude Code mods have been one of the best updates so far ClaudeAI | YareYareDaze007 | 1 | 2 |
| 🟠 reddit | I approved an agent’s “oc delete —all” without reading it, so I built guardrails (and 10 other mods) with Claude Code’s new function hooks ClaudeAI | Sea-University-7237 | 0 | 16 |
| 🟠 reddit | mods are really powerfull ClaudeAI | adminvasheypomoiki | 17 | 6 |
| 🟠 reddit | My Claude Code status line now runs as a mod, so I can finally see my limits in the desktop app ClaudeAI | uppinote | 0 | 2 |
| 🟠 reddit | I gave my Claude Code subagents names (Turing, Magellan, Holmes) and a pane that lists them - named subagents mod ClaudeAI | midgyrakk | 0 | 1 |
| 🟠 reddit | Claude Code mods are kinda insane ClaudeAI | ITower__Education | 1 | 7 |
| 🟠 reddit | Are the new Code features about innovation or ecosystem lock-in? ClaudeAI | EightFolding | 19 | 25 |
| 🟠 reddit | 394 subagents in ten minutes locked me out of Claude Code, so I built a mod that asks first ClaudeAI | rbartoli | 0 | 11 |
| 🟠 reddit | I made a claude code mod that uses Haiku 5.5 (or Jev) to pick the best model and effort for your task. (and more...) ClaudeAI | Intelligent-Crew-576 | 245 | 73 |
| 🟧 hn | Agent-config&Claude Code mods | FunShot | 2 | 1 |
| 🟧 hn | Show HN: Context Diet – trims tool output before it floods Claude Code's context | hy4hy | 1 | 0 |
2026-10-10T05:02:27Z
Periphery actively expanding with four new substantive mods (agent-usage-guard for spend/concurrency limits, Haiku 5.5 model router at 181 pts/64 comments — velocity spike, Context Diet for output trimming, agent-config integration) plus established OSS adopter Repowise Lens (7k stars) and plugin-author migrations. Measured heat 93rd percentile, magnitude-valve eligible across 3 platforms. Yet both core signals unfired: no mod with real adoption traction, and no outside security voice naming the self-approve/secret/spend supply-chain risk. Scott's dated-receipts window stays open. Dormancy holds but periphery not at rest.
2026-10-10T01:44:12Z
evidence attached: hn.story.50024608 — Concrete third-party mod using Claude Code's new mods API to trim tool output, directly illustrating the mods ecosystem the case tracks.
2026-10-09T19:58:39Z
evidence attached: hn.story.50024345 — Community plugin for the Claude Code mods/skills system, extends the mods ecosystem covered by the open case.
2026-10-09T19:58:38Z
evidence attached: reddit.post.1x1nnkn — Community-built mod using Haiku 5.5 for dynamic model/effort routing — concrete example of the mods extension system in action.
2026-10-09T19:58:38Z
evidence attached: reddit.post.1x1r82v — Concrete example of a builder using the new Claude Code mods system (agent-usage-guard) to enforce subagent concurrency and spend limits — directly illustrates the mods adoption and trust-surface dynamics the case tracks.
2026-10-09T03:38:18Z
grounded: converges/high — Anthropic shipped exactly the in-process third-party TypeScript middleware surface Scott's containment canon maps: mods act as the user, pre-approve permission
2026-10-09T03:25:25Z
New discussion post (1x14s77, 16 pts/22 comments) debates ecosystem lock-in vs innovation around mods and cloud sessions — meta-discourse, not a traction mod, security analysis, or marketplace incident. No pre-declared signal fired: still no mod with real adoption, no outside security voice naming the self-approving/secret/spend surface a supply-chain risk. Case remains dormant at 204h; velocity 0.17 pts/h vs 121 peak, 50th percentile is cohort decay. Both open halves wait on external crystallization.
2026-10-08T23:06:43Z
evidence attached: reddit.post.1x14s77 — User discusses Anthropic's new 'javascript plugins that run in Code' (mods) and cloud sessions, directly referencing the mods feature and Claude Projects.
2026-10-07T17:19:45Z
The newest datum — a casual user's first-try in-session mod build plus their own 'not sandboxed, sees prompts and keys' caution — adds no new evidence class: weakest-tier adoption and organic wariness were both already counted, so nothing is material and the quiet-age clock keeps running. What it does show is that the trust surface has become folk knowledge among casual Pro-tier users, a precondition for the supply-chain crystallization, not the crystallization itself; dormancy holds with both open halves (no traction mod; no outside security voice) waiting on external events, and the 45th peer percentile is a cohort-decay artifact at 171h, not a reheat.
2026-10-07T16:35:56Z
evidence attached: reddit.post.1x00yp0 — Hands-on adoption of mods plus the user explicitly flagging the unsandboxed prompts/keys trust surface — both resolution dimensions of the open case.
2026-10-07T08:35:01Z
The new datum — a weakest-tier named-subagents UI mod (0 pts, 1 comment) — adds no evidence class to a mix already counted, and with velocity now at literal zero (0.0 pts/h vs ~109 peak; peer percentile 22.2, down from 82; 'steady' momentum a zero-rate artifact) the periphery has gone from trickling to at rest: the case enters dormancy because the periphery stopped, not because either open half resolved. Signals 2–4 and the supply-chain half now wait on external crystallization (a traction mod, a security voice, a marketplace or prompt-transmitted-mod incident) rather than organic drift; nothing here is material, so the quiet-age clock keeps running.
2026-10-07T08:25:41Z
evidence attached: reddit.post.1wzqp1o — A third-party mod redrawing Claude Code's UI and wrapping subagent control is a concrete adoption instance of the mods deep-extension path and its enlarged trust surface.
2026-10-07T04:51:00Z
The new datum is the first established plugin author migrating an existing plugin to a mod specifically for desktop reach (claude-dashboard's status line) — mods confirmed as a migration target for working plugin authors, not just a new-toy surface, deepening the adoption half at weakest tier without firing any pre-declared signal. Both open halves unchanged: no mod with real traction, no outside security voice naming the self-approve/secrets/spend surface. Velocity remains residual tail — measured_heat's 82nd peer percentile and 'accelerating' momentum are cohort-decay artifacts at 158h age (0.83 pts/h vs ~109 peak), not new spread — so heat stays low and the case drifts toward dormancy unless a signal or the supply-chain half fires.
2026-10-07T03:33:13Z
evidence attached: reddit.post.1wzhpjb — Third-party plugin author porting claude-dashboard's status line into a pane/band mod is concrete adoption evidence for mods as the deep-extension path.
2026-10-06T22:30:18Z
The new datum is the second no-hand-written-code mod and the first shared without any repository — code transmitted as screenshots plus an 'ask your Claude to build it' prompt, a provenance channel weaker than any marketplace — though at 6 pts/0 comments it fires nothing. Otherwise tail drift (0.5 pts/h vs ~109 peak) plus the guardrail author's 0.2.0 reply making the guardrail protect its own settings from the agent — the periphery answering the tamper-resistance question at practitioner level; both open halves (no traction mod, no outside security voice) unchanged.
2026-10-06T20:42:17Z
evidence attached: reddit.post.1wzcz0q — First community-built third-party mod (HUD for cache/quota) via the plugin-authoring skill — earliest adoption evidence for the mods deep-extension case.
2026-10-06T18:31:23Z
The new datum is the periphery's first incident-motivated guardrail mod — built after the author approved an agent's 'oc delete --all' unread and lost half a namespace — which deepens the established UI-toys→middleware drift without adding a new evidence class; its comment thread's sharpest line (can the agent edit or disable its own guardrail toggles — 'fixed the rule' vs 'worked around it'?) is the nearest any periphery voice has come to the enforcement-integrity edge, but it's a practitioner remark, not a security voice, so the security half stays unfired. Both open halves unchanged — no real-traction mod (signal 2), no outside voice naming the self-approve/secrets/spend surface, Scott's dated-receipts window still eroding — and 0.33 pts/h tail drift (hottest object a residual 64th-percentile comment tail, not new spread) keeps heat at low on a thin-but-still-trickling periphery.
2026-10-06T16:42:15Z
evidence attached: reddit.post.1wz4dp5 — First-person adoption of mods building tool-call guardrails after a real destructive-command incident — evidence for both the adoption path and the guardrail use-case in the mods hypothesis.
2026-10-06T12:18:32Z
The new datum is the first testimonial from a casual non-developer Pro user calling mods one of the best updates ever — it mildly widens who finds mods valuable beyond the developer-tooling niche, but at weakest-tier reception (1 pt, 2 comments) it fires no pre-declared signal and changes neither open half. Everything else is engagement drift on existing objects (handoff-compact 24→26, usage band 8→9); ~142h in, still no mod with real traction, no second established-tool adopter, and no outside security voice naming the self-approve/secrets/spend surface, so Scott's dated-receipts window keeps eroding.
2026-10-06T11:33:25Z
evidence attached: reddit.post.1wyzz4j — First-hand positive adoption experience with mods is direct uptake evidence for whether mods become the deep-extension path.
2026-10-06T04:55:13Z
The Repowise Lens attach upgrades the adoption half's quality rather than its quantity: the first mods adoption by an established OSS project with existing distribution (7k stars), continuing the drift from UI toys toward tool-vendor middleware — it brushes pre-declared signal 3 (influential entrant) but at weakest-tier reception fires nothing, so the case stays corroborated on dormant watch instead of accelerating. Everything else is tail-drift on existing objects (catalog post decaying, usage-band post inching up), heat holds at low; the security half is untouched — still no outside voice names the self-approve/secrets/spend surface, so Scott's dated-receipts window keeps eroding.
2026-10-06T03:33:52Z
evidence attached: reddit.post.1wyrmj7 — A 7k-star code-intelligence tool shipping Lens on the new mods API is direct third-party adoption evidence for mods as the deep-extension path.
2026-10-05T22:13:31Z
The kill-switch attach adds a genuinely new dimension: mods sit behind a remote rollout gate that already misfires (a session silently loads with mods off because 'the rollout switch was saved off by an earlier session and is not refreshed') — concrete adoption friction, and a double-edged governance datum since Anthropic demonstrably holds a deterministic remote gate over the extension layer but it is unreliable. The velocity trigger is the hook-guard post's comment tail (13.5x off a near-zero peer baseline, ~3.5 pts/h absolute, one existing object) rather than new periphery, so heat stays low and both open halves are unchanged: signals 2-4 unfired, still no outside security voice names the self-approve/secrets/spend surface.
2026-10-05T20:39:22Z
evidence attached: reddit.post.1wyfa5m — First-hand error output reveals mods have a remote kill-switch rollout gate that already misfires and confuses early adopters — direct context for the mods adoption/trust-surface case.
2026-10-05T14:28:20Z
The catalog-driven velocity spike has receded (2.0 pts/h vs ~4.7 when medium was set; the catalog post's comments net-declined, and this look added no new mods, communities, or outlets — only engagement drift on existing objects), so the ecosystem-forming question returns to dormant watch rather than active spread, and heat cools medium→low; the 98th-percentile peer rank is a within-cohort rank among ~5-day-old mostly-dead posts and doesn't override the absolute taper. The one substantive attach — first-party measurement that hook guards are leaky (bypass mode routes the model around Read hooks via cat/sed) — sharpens the guarding half's meaning (behavioural guards measurably bypassed, which is exactly the gap mods' mechanical interception addresses) without moving either open half: signals 2-4 unfired, and still no outside security voice names the self-approve/secrets/spend surface, so Scott's dated-receipts window stays open but keeps eroding.
2026-10-05T13:28:23Z
evidence attached: reddit.post.1wy76rw — First-party measurement of hook-guard usage (448 blocks/76 sessions) and its leakiness — bypass mode routes the model around Read hooks via cat/sed — direct context for mods' tool-call-guarding role.
2026-10-05T02:27:10Z
A third-party catalog/marketplace (baselane-sh, ~100 mods, /plugin marketplace add install path) recommended to a general Reddit audience is the first weak fire of pre-declared re-raise signal 1: the adoption half now has a discovery layer and an order-of-magnitude larger catalogued periphery, shifting the case's question from 'can people write mods' toward 'is a mod ecosystem forming' — though catalog contents and install traction are unverified. The supply-chain half is untouched: a commenter's organic wariness about running third-party code is the seed of the framing, but still no security voice names the self-approving/secret/spend surface, so Scott's dated-receipts window stays open. Heat moves low→medium on the 18x velocity spike off the case's floor and a 90th-percentile peer object — periphery expanding (new catalog, new audience) — but no platform domination and modest absolute rate (4.67 pts/h vs 81 peak) keep it below high.
2026-10-05T00:24:09Z
evidence attached: reddit.post.1wxtzxd — Community post plus a third-party catalog of ~100 mods documents organic adoption spreading and the enlarged trust surface (install-time access display, guard mods) the open case is tracking.
2026-10-04T22:47:15Z
grounded: converges/high — Anthropic shipped exactly the surface Scott's containment canon maps: first-party docs confirm in-process third-party TypeScript that acts as the user, pre-appr
2026-10-04T22:38:48Z
The eleventh independent mod (document-review UI in the TUI, authored with no hand-written code, weakest-tier reception at 1 pt) is more of the same trickle and fires none of the four re-raise signals, so the case's meaning is unchanged — eleven weak builds confirm people can write mods but say nothing new about either open half. What ages rather than changes: ~104h post-launch, still no outside voice has named the self-approving/secret/spend surface a supply-chain risk, so Scott's dated-receipts window stays open but keeps eroding.
2026-10-04T22:25:54Z
evidence attached: reddit.post.1wxs08o — Third-party builder shipping a document-review mod is a small but direct adoption signal for the mods extension path.
2026-10-04T19:40:44Z
The tenth independent mod (live usage/context band with auto/manual compaction) is more of the same trickle — weakest-tier reception, docs-tutorial-adjacent utility, no re-raise signal — so the case's meaning is unchanged. What ages rather than changes is the open security half: at ~102h post-launch still no outside voice has named the self-approval/secret/spend surface a supply-chain risk, so Scott's dated-receipts window remains open but is eroding.
2026-10-04T19:24:43Z
evidence attached: reddit.post.1wxntoy — Third-party builder shipped a working mod (live usage/context UI, compaction controls) within a day of launch — direct adoption evidence for mods as the deep-extension path.
2026-10-04T08:26:38Z
The ninth independent mod is a docs-tutorial derivative (status band via ui.render/element tree, arrived via a newsletter mention) — adoption trickles on at weakest tier but the case's meaning is unchanged: no re-raise signal fired, both open halves (dominant-extension-path, security-voice) remain open, and Scott's dated-receipts publishing window stays intact. Attention is at floor (~0.33 pts/h vs ~44.8 peak at 90h), so heat drops to low; the case remains a corroborated thin builder pattern in dormant watch on its pre-declared signals.
2026-10-04T08:23:29Z
evidence attached: reddit.post.1wx9umm — Early independent third-party build log with concrete mod API specifics (ui.render, element tree) — first adoption data for the watched deep-extension path.
2026-10-04T05:33:42Z
Meaning unchanged since the last look: the only new evidence is a Reddit link-share of the already-canonical mods docs ('Feels like mods are like hooks 2.0?'), and handoff-compact's 20→23 pt drift is engagement, not substance — no re-raise signal fired. What changed is temperature: attention has fully decayed (~0.17 pts/h vs ~43 peak at 87h age, percentile 38 on a near-zero rate), so the case cools from high to dormant-watch — a corroborated thin builder pattern with both open halves (dominant-extension-path, security-voice) intact and Scott's dated-receipts publishing window still open.
2026-10-04T05:23:32Z
evidence attached: reddit.post.1wx7esq — shared external link with case evidence
2026-10-03T21:02:12Z
relevance=high case never alerted; deterministic escalation to deliver
2026-10-03T20:26:17Z
evidence attached: reddit.post.1wwwkfs — Concrete production-grade use of mods' tool-result rewriting — fixing the truncated-xcodebuild-log failure — evidence that the mods extension path is producing real harness utilities.
2026-10-03T19:04:45Z
Seventh independent mod — Reporails' minesweeper, the first distributed via its own plugin marketplace and shipped with a tmux testkit and dev.to writeup — deepens the thin-builder periphery but meets none of the four pre-declared re-raise signals, and its reception is weakest-tier (1 pt HN, 0 pts Reddit). Still no security voice on the self-approving/secret/spend surface, so Scott's dated-receipts publishing window stays open; handoff-compact's 14→20 pt drift is engagement, not substance.
2026-10-03T18:25:45Z
evidence attached: hn.story.49946184 — Third-party mod published right after launch is early adoption evidence for whether mods become the deep-extension path.
2026-10-03T18:25:45Z
evidence attached: reddit.post.1wwta3j — Early third-party mod shipping through the plugin marketplace (plus tmux-driven self-testing) — weak but real adoption evidence for the mods deep-extension case.
2026-10-03T13:36:27Z
Sixth independent mod arrived — CodeCraft, a Minecraft-style HUD redraw (0 pts, 3 comments, 0.5 ratio, weakest-received yet, and built by Claude itself per the docs' ask-Claude path) — which confirms rather than extends the thin-builder-pattern reading. It meets none of the pre-declared re-raise signals (no marketplace, no traction, no influential entrant, no security voice), so low heat holds despite the fresh substantive-evidence tag and the trust-surface publishing window stays open.
2026-10-03T13:24:17Z
evidence attached: reddit.post.1wwm5dt — Early third-party mod built on the new Mods feature, directly exercising its UI-redraw capability — small but real adoption evidence for the deep-extension-path case.
2026-10-03T12:47:12Z
Periphery production resumed after the declared stop: a fifth independent mod, handoff-compact, and the first built as an installed utility (auto handoff + /clear at autocompact, motivated by measured token waste) rather than a show-and-tell — a modestly stronger adoption datum that nonetheless meets none of the pre-declared re-raise signals (no marketplace, no traction at 4pts/1 comment, no influential entrant). The trust-surface half is untouched: still no outside voice naming the self-approving/secret/spend surface a supply-chain risk, so Scott's dated-receipts window stays open; the docs resubmission on HN is engagement noise.
2026-10-03T12:24:47Z
evidence attached: hn.story.49943177 — Official claude.com mods documentation — the primary artifact of the open case.
2026-10-03T12:24:47Z
evidence attached: reddit.post.1wwk4y5 — A third-party mod automating pre-autocompact handoff documents is concrete adoption evidence for mods as the deep-extension path and touches the hot agent-memory topic.
2026-10-03T05:34:04Z
The quiet look the last reprice conditioned on has arrived: the only new evidence is a duplicate resubmission of the getting-started guide (2 pts, 0 comments) — not a new mod, not a security voice, so it is engagement noise, not substance. Periphery production has stopped, so the medium hold lapses and the case cools to low while staying corroborated and open on both hypothesis halves; the still-unclaimed publishing window on the trust surface is what keeps it alive rather than expired.
2026-10-03T00:25:46Z
evidence attached: hn.story.49940121 — shared external link with case evidence
2026-10-02T16:58:51Z
Fourth independent mod — statusline-anywhere, notably reaching the desktop app — extends the builder pattern to a second surface but is the same thin character of evidence (2 pts, 0 comments), so the assessment is unchanged: a reproducible but low-traction extension pattern, not adoption at scale, and still no outside voice naming the self-approving/secret/spend trust surface. Periphery is still producing implementations, which holds medium heat against near-dead numbers, but production is slowing (one thin mod this cycle vs. two last); a quiet next look cools this to low.
2026-10-02T16:26:23Z
evidence attached: hn.story.49934608 — Early third-party mod built on the new modding API — and extending it to the desktop app — is direct adoption evidence for the mods episode.
2026-10-02T15:42:12Z
Two more independent mods shipped within a day of each other — an observability UI mod and a multi-harness delegation mod — moving the adoption half from 'one early port' to a reproducible builder pattern: three third-party implementations in ~48h, though all thin (1-3 pts, zero comments). Meanwhile raw attention collapsed to ~0.5 pts/h from a ~17 peak. That divergence — belief-side substance accruing while the audience-side fades — plus the still-unnamed trust surface keeps this on medium watch rather than cooling it: the periphery is genuinely still expanding with implementations, and the publishing-window half of the hypothesis remains untouched by any outside voice.
2026-10-02T15:25:28Z
evidence attached: hn.story.49934033 — Another third-party mod (multi-harness delegation) shipped on the new extension surface; each notable mod bears on whether mods become the adopted deep-extension path.
2026-10-02T15:25:28Z
evidence attached: hn.story.49934165 — Third-party mod built on the new hooks with the author discussing the mod-building experience is early adoption evidence for mods as the deep-extension path.
2026-10-02T00:43:30Z
First independent third-party implementation — Pi-autoresearch ported 1:1 onto the mods API within a day of launch — upgrades mods from launch announcement to demonstrated deep-extension path, and the retrieved docs text now confirms the trust surface first-party (mods can approve calls an ask rule or PreToolUse hook would block, read secrets, spend usage). The episode's open half narrows to whether anyone outside Anthropic names this a supply-chain risk — none yet do.
2026-10-01T23:31:30Z
evidence attached: hn.story.49927599 — A third party porting an entire autonomous-research harness 1:1 via the mods API is concrete adoption evidence for mods as the deep-extension path the case is tracking.
2026-10-01T21:48:44Z
origin walked (opencode/cheap-glm, conf 0.85): anchor hn.story.49925800 -> echo.blog.751220d622 by Anthropic
2026-10-01T21:01:48Z
grounded: converges/high — Anthropic's move from shell hooks to in-process TypeScript middleware that intercepts tool calls and prompts converges with Scott's manners-vs-physics / determi
2026-10-01T20:54:14Z
case created — One launch episode across three objects (announcement, docs, tutorial); the scout's two creates and orphan attach are the same release and consolidate here.