ClaudeMap

Claude Code Mods Docs

Official docs for Claude mods — plugin event handlers that run inside Claude Code itself, drawing UI and reshaping tool calls.

Plugins & Agentsofficialmodsclaude-codepluginsdocumentation
Visit project

Anthropic's documentation for the Claude mods platform: a mod is a plugin made of JavaScript or TypeScript event handlers that Claude Code calls in its own process when events happen — a tool call, a submitted prompt, a part of the interface being drawn — and each handler can watch the event, change it, or take it over. The docs cover creating mods, the mods API, testing, an organization admin guide, a comparison with settings hooks, skills and MCP servers, and the built-in mods such as You should know. Mods are on by default from Claude Code v2.1.287 (terminal) and v2.1.286 (Desktop); the early-access flag CLAUDE_CODE_ENABLE_FUNCTION_HOOKS is ignored from v2.1.287.

What it does

  • Full doc set for the mod platform: overview, create, build, test, API reference, plus a guide to managing mods across an organization
  • Mods are on by default — terminal needs Claude Code v2.1.287+, the Desktop app v2.1.286+, and the VS Code extension panel v2.1.299+
  • claude plugin validate prints a mod's hooks: and calls: lines — the events it handles and the $ calls it makes — before any mod code runs
  • A comparison table sorts out mod vs settings hook vs skill vs MCP server, and the docs introduce the built-in mods, including You should know

When to use it

The starting point when settings hooks or skills can't reach far enough — custom panes and prompt bands in the terminal, tool-call rewriting, agent spawning inside Claude Code. Also the reference org admins need for gating mods, and the trust checklist to read before installing third-party ones.

Getting started

No install — it is a documentation site. Start at Mods overview; to inspect a mod before installing it, clone its repo and run:

claude plugin validate ./some-mod

# to see which mods a session loaded:
/plugin

Things to know

Mods run with your permissions: the docs are explicit that a loaded mod can act on your machine as you, read environment variables and settings files (including API keys), and see every prompt and tool call — install only from authors and marketplaces you trust. Drawing is narrower than hooks: it appears in the terminal, Desktop and VS Code extension, while headless surfaces such as claude -p and the Agent SDK don't run mod drawing. The old CLAUDE_CODE_ENABLE_FUNCTION_HOOKS flag is ignored since v2.1.287 — the docs say to remove it.

Charted

Related on the map

  • clawd-conduit

    Plugin / Agent

    Wire all 15 Claude Code hook events into the Clawd on Desk desktop pet — and turn permission requests into a blocking desktop card.

    • hooks
    • desktop
    • notifications
    • claude-code
    View

  • CometixCode

    Plugin / Agent

    An unofficial Rust 1:1 reimplementation of the Claude Code terminal UI, ported file-for-file onto an iocraft TUI framework.

    • terminal-ui
    • rust
    • reimplementation
    • unofficial
    View

  • Abide

    Plugin / Agent

    Hook-level enforcement for the natural-language rules in AGENTS.md and CLAUDE.md — every edit is judged and violations are repaired in the same turn.

    • hooks
    • code-review
    • rules
    • agents-md
    View