A new generator (BuiltinToolInputs) writes a claude-code.d.ts declaration file merging built-in tool input schemas into ToolCallInput, similar to the existing MCP tool-input declaration file. This lets TypeScript users narrow e.tool === "Bash" etc. to typed arguments for built-in tools, not just MCP tools. The built-in plugin-types local command now writes both claude-code.d.ts and claude-code-mcp.d.ts, whereas previously it only wrote the MCP tool inputs file.
Names in the bundleplugin-typesclaude-code.d.tsclaude-code-mcp.d.ts
Documented inclaude-code/plugins/mods/reference
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude-code.d.ts, on Mods reference.
The complete reference is Claude Code's [TypeScript declarations for mods](https://github.com/anthropics/claude-code/blob/main/mods/types/claude-code.d.ts), which describe every event, method, and element, with examples. The copy on GitHub…plugins/mods/reference see the edit
Added since
A small documentation edit on Create a mod touched a line naming claude-code.d.ts after this was published.
Each time Claude Code loads or reloads a mod from a directory you pass to `--plugin-dir`, or a mod [Claude wrote for you](#ask-claude-for-a-mod), it writes TypeScript declaration files, ending in `.d.ts`, into `.claude-plugin/types/` insid…plugins/mods/create see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Create a mod touched a line naming claude-code.d.ts after this was published.