awesome-claude-code-function-hooks

Claude Code function hooks that are worth installing.

Not shell hooks. Nothing here is a command in settings.json that Claude Code shells out to. A function hook is a TypeScript module that Claude Code loads and runs inside the session: no subprocess, no JSON on stdin, no exit code. It sees each event as it happens, it can change the event, and it can draw in the terminal.

These are the function hooks proposed in anthropics/claude-code#91870. Read that issue first. It has the design, the videos and the architecture document, and it is where you say whether you want this to ship.

Turn the feature on first

Function hooks are early access. They are off by default, and a plugin that uses one does nothing at all until you turn them on. Do this before you install anything here.

Put it in your user settings, at ~/.claude/settings.json, so every project gets it:

{
  "env": {
    "CLAUDE_CODE_ENABLE_FUNCTION_HOOKS": "1"
  }
}

Or set it for one run, to try it without changing a setting:

CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 claude

The API is early access, so it moves. A release can rename an event or change a payload. Pin what you rely on.

Install

This repo is a plugin marketplace. Add it once, then install what you want.

/plugin marketplace add ray-amjad/awesome-claude-code-function-hooks
/plugin install secret-redactor@awesome-claude-code-function-hooks
/plugin install vercel-deploy-status@awesome-claude-code-function-hooks

The function hooks

Plugin	What it does
secret-redactor	Swaps every secret, email address and IP address for a stable placeholder before the model reads it, then puts the real value back on the way into a tool call. Nothing goes to disk.
vercel-deploy-status	Pins the Vercel deploy queue of the linked project under the prompt: one line per deploy that is queued, building or just finished, with its phase and elapsed time. A git push or a gh pr merge wakes it.

Work on this repo

The type declarations are not in git. Claude Code writes them, and every release rewrites them, so a checked-in copy goes stale and lies to you.

Make them yourself. In Claude Code, from the root of this repo, run:

/plugin-types

That writes types/claude-code.d.ts. Every plugin's tsconfig.json points at it with "include": ["../../types", "hooks"]. Do this first, or tsc reports that h, Box, Text and the claude-code module do not exist.

Never hand-edit types/claude-code.d.ts. Run /plugin-types again instead.

Then check a plugin. Each one has the same three steps:

node --experimental-strip-types plugins/secret-redactor/test/detect.test.mts
claude plugin validate plugins/secret-redactor
npx tsc -p plugins/secret-redactor/tsconfig.json

Run a plugin without installing it:

claude --plugin-dir plugins/secret-redactor

Add a hook

1. Make plugins/<name>/ with .claude-plugin/plugin.json and hooks/hooks.json.
2. Point hooks.json at your module: { "modules": ["./your-hook.ts"] }.
3. Copy plugins/secret-redactor/tsconfig.json. It already points at ../../types.
4. Add a test/ that runs on plain node --experimental-strip-types, with no dependencies.
5. Add the plugin to .claude-plugin/marketplace.json and to the table above.

License

MIT. See LICENSE.