echook

Audio and out-of-band notifications for Claude Code, Cursor IDE, and Codex CLI.
You configure it by talking to your agent — every setting is one sentence, not a JSON edit.
Hear when your agent finishes, needs permission, or hits a rate limit — plus an optional context-usage status line.

_{v6.4.0 — 37 hook events and 30 matcher variants across all three editors · 2 audio themes · webhooks · TTS · rate-limit alerts · status line. Renamed claude-code-audio-hooks → echook (Echo + Hook) in 5.2.1; existing installs keep working. Full history in the CHANGELOG.}

Share This Project

Promotional Video

promo-video.mp4

^{Built with Remotion, Claude Code, ElevenLabs & Suno. Source: echook-promo-video}

🤖 Install and configure this by asking your agent — there is no hand-edit path

Humans: don't install or configure echook by hand. Point your AI agent — Claude Code, Cursor, or Codex — at this repo and say:

"Install echook from github.com/ChanMeng666/echook and set it up for me."

Your agent reads the docs, runs every command, verifies the result, and reports back. The agent-facing source of truth is AGENTS.md + llms.txt + the live audio-hooks manifest. Every capability is a non-interactive subcommand that takes and returns JSON, and hand-editing user_preferences.json is unsupported by design. Two things an agent still can't do for you: type /reload-plugins on Claude Code (no CLI equivalent), and restart the editor once on the Cursor and Codex install paths.

All a human needs to know is what echook does — skim Key Features below — so you can ask your agent for it in plain English: "mute audio for an hour", "switch to chimes", "watch my .env file", "put a context-usage bar in my status line". Not sure what's possible? Just ask your agent "what can I configure in echook?"

Table of Contents

What's New
Key Features
Get Started
Talk to It — Natural Language Control
How It Works
Platform Support
Help, Uninstall & Documentation
License
Author

What's New

Latest: v6.4.0 — per-variant toggles + the full Notification matcher set. Each of the 30 matcher variants is now switchable on its own (before, every variant of an event shared one flag), the four Notification matchers echook was missing are registered, and filters.stop.skip_if_background_tasks_running keeps the turn-end sound quiet while subagents are still running. All new variants ship opt-in.

Earlier highlights: v6.3.4 removed worktree_create / worktree_remove — they hijacked Claude Code's own provider hook and broke worktree isolation — taking the event count from 39 to 37 · v6.3.0 grew the status line to 29 segments · v6.2.0 added 13 lifecycle events, including Cursor's granular per-tool-type events so shell commands, MCP calls, and file reads each get a distinct sound.

📜 Full version history → CHANGELOG.md · GitHub Releases

Key Features

echook does exactly two things: (1) tells you what just happened in your AI session when you're not watching the window — a sound at your desk, a spoken summary when you're away, a desktop toast or webhook when you're in another app — and (2) a status line that keeps the facts you need pinned to the bottom of the terminal.

If you're comparing. Claude Code can already ring the terminal bell, pop a desktop notification in Ghostty/Kitty/iTerm2, and push to your phone, and Anthropic publishes a four-line afplay hook you can paste into settings.json. If one sound for everything is enough, that is the right answer and it costs nothing. Others cover this ground too: peon-ping supports far more harnesses and groups events into 7 sound categories; claudio does Claude Code + Codex audio; anotifier does desktop/phone notifications for Claude Code, Codex, Gemini and Cursor; and Cursor 3.2.16+ executes Claude Code hooks natively. echook's difference is which of 37 events you hear, per-event on all three editors, configured by talking to your agent rather than by editing JSON.

🔔 Audio & out-of-band notifications

Hear (or get pinged) the moment your agent finishes, asks for permission, fails a tool, or hits a rate limit — so you can walk away and trust you'll be called back.

Channel	What it's for
Audio	A sound at your desk the instant something needs you. Two themes — voice or chimes.
Desktop toast	A glanceable popup when you're in another window.
TTS	Speaks a sanitized summary of Claude's actual final message when you're away from the screen.
Webhook	Slack / Discord / Teams / ntfy / any HTTP endpoint — get alerts on your phone.

📊 Status Line — startup-banner pin + context monitor

Pins your Claude Code startup banner at the bottom (so it never scrolls away) and adds real-time context-window and quota bars — color-coded warnings before Claude enters the "agent dumb zone". Auto-reflows to fit any terminal width, so nothing is truncated.

Color	Context used	Meaning	Action
🟢 Green	< 50%	Safe — agent performs well	Keep working
🟡 Yellow	50–80%	Caution — entering the "dumb zone"	`/compact` or `/clear` soon
🔴 Red	> 80%	Danger — frequent errors	`/compact` immediately

29 customisable status-line segments

A few of the highlights (run audio-hooks statusline segments for the full live catalog):

Segment	Shows
`model`	Model name (e.g. `[Opus 4.8 (1M context)]`)
`effort` / `thinking`	Reasoning effort (`🧠 high`) / extended-thinking flag
`cc_version`	Claude Code's own version (`⚡ CC v2.1.193`)
`cwd` / `repo`	Working directory / git remote `owner/name`
`session_name` / `agent` / `output_style` / `vim`	Session label / `--agent` name / output style / vim mode
`branch` / `git_dirty` / `worktree`	Git branch / uncommitted-change count / managed worktree
`pr` / `added_dirs`	Pull-request number + review state / `/add-dir` count
`api_quota` / `weekly_quota`	5-hour & 7-day rate-limit bars + reset times
`context` / `tokens` / `exceeds_200k`	Context bar (+ tokens, `/compact` hint) / cache-hit ratio / >200K flag
`cost` / `duration` / `api_time` / `burn_rate`	Cost + lines diff / wall-clock time / API-wait share / $/hour
`version` · `sounds` · `webhook` · `theme` · `snooze`	echook version · sound count · webhook · audio theme · mute countdown

Most richer segments self-omit when Claude Code doesn't supply their data, so a plain session stays clean. Pick segments with visible_segments (whitelist) or drop a few with hidden_segments (blacklist). Each logical line auto-reflows into as many rows as your terminal width needs — segments are never split, so nothing is cut off. Pin the width with statusline_settings.max_width.

Codex note: Codex's status line is not command-backed — it only accepts a fixed list of built-in item IDs. echook can't render custom Codex segments, but it can curate the list so it stops truncating: audio-hooks statusline codex apply --preset balanced.

📖 Full reference: docs/STATUS_LINE.md — every segment, both editors, all flags.

🎚️ More

Feature	What it does
37 hook events · 30 matcher variants	Across Claude Code, Cursor & Codex — session start, tool use, permission requests, rate-limit warnings, and Cursor's granular shell/MCP/file events. The three editors document 63 events between them; echook maps 37, each to its own sound. 3 on by default; toggle any in plain English.
2 audio themes	`default` = ElevenLabs Jessica voice ("Task completed") · `custom` = modern UI chimes. Say "switch to chimes".
Rate-limit alerts	One-shot warning at 80% / 95% of your 5-hour or 7-day quota — warned once per threshold, never spammed.
Webhooks	Versioned `audio-hooks.webhook.v1` payload, fire-and-forget, never blocks a hook.

Full hook events table (37 events, 30 matcher variants)

Hook	Default	Audio file	Native matchers
`notification`	on	notification-urgent.mp3	`permission_prompt` / `idle_prompt` / `auth_success` / `elicitation_dialog` / `elicitation_complete` / `elicitation_response` / `agent_needs_input` / `agent_completed` (last four v6.4, off by default)
`stop`	on	task-complete.mp3
`subagent_stop`		subagent-complete.mp3	agent type
`permission_request`	on	permission-request.mp3	tool name
`permission_denied`		permission-denied.mp3
`task_created`		task-created.mp3
`task_completed`		team-task-done.mp3
`session_start`		session-start.mp3	`startup` / `resume` / `clear` / `compact`
`session_end`		session-end.mp3	`clear` / `resume` / `logout` / `prompt_input_exit`
`pretooluse` / `posttooluse`		task-starting.mp3 / task-progress.mp3	tool name
`posttoolusefailure`		tool-failed.mp3	tool name
`userpromptsubmit`		prompt-received.mp3
`subagent_start`		subagent-start.mp3	agent type
`precompact` / `postcompact`		notification-info.mp3 / post-compact.mp3	`manual` / `auto`
`stop_failure`		stop-failure.mp3	`rate_limit` / `authentication_failed` / `billing_error` / `server_error` / `unknown`
`teammate_idle`		teammate-idle.mp3
`config_change` · `instructions_loaded`		config-change.mp3 · instructions-loaded.mp3
`elicitation` / `elicitation_result`		elicitation.mp3 / elicitation-result.mp3
`cwd_changed` · `file_changed`		cwd-changed.mp3 · file-changed.mp3	literal filenames
`setup` (v6.2, Claude Code)		setup-ready.mp3	`init` / `maintenance`
`user_prompt_expansion` · `post_tool_batch` · `message_display` (v6.2)		(per event)
`shell_before` / `shell_after` (v6.2, Cursor)		shell-starting.mp3 / shell-done.mp3
`mcp_before` / `mcp_after` (v6.2, Cursor)		mcp-starting.mp3 / mcp-done.mp3
`file_read` · `agent_response` · `agent_thinking` · `workspace_open` · `tab_file_edit` (v6.2, Cursor)		(per event)

Run audio-hooks hooks list for the live state, or see the CLI & Configuration Reference.

Get Started

You don't follow install steps yourself. You tell your AI agent what to do in plain English, and it runs every command and reports back.

flowchart TB
    REPO["github.com/ChanMeng666/echook<br/>(source + GitHub Releases)"]

    REPO --> CCP["Claude Code<br/>plugin marketplace"]
    REPO --> CURB["Cursor 3.2.16+<br/>auto-bridge (Path A)"]
    REPO --> CURN["Cursor native<br/>install --cursor (Path B)"]
    REPO --> CXP["Codex plugin<br/>marketplace"]
    REPO --> CXN["Codex native<br/>install --codex"]

    CCP --> CLI["audio-hooks CLI<br/>+ JSON + /audio-hooks SKILL<br/>(identical everywhere)"]
    CURB --> CLI
    CURN --> CLI
    CXP --> CLI
    CXN --> CLI

    CLI --> OUT["37 hook events · 30 variants · 2 themes · webhooks<br/>TTS · rate-limit alerts · status line"]

    style REPO fill:#4A90E2,color:#fff
    style CLI fill:#7ED321,color:#000
    style OUT fill:#F5A623,color:#000

Find your editor, paste the prompt into your agent, done:

Your editor / CLI	Tell your AI agent
Claude Code	"Install the audio-hooks plugin from `github.com/ChanMeng666/echook`." (Then type `/reload-plugins` once — Claude Code has no CLI equivalent for it.)
Cursor (with Claude Code)	Nothing to install — Cursor 3.2.16+ auto-bridges the Claude Code plugin. "Run `audio-hooks status` and confirm `editor_targets.cursor.state` is `bridged-via-claude-code`."
Cursor (without Claude Code)	"Clone `github.com/ChanMeng666/echook` into `~/audio-hooks`, run `python ~/audio-hooks/bin/audio-hooks install --cursor`, then verify with `audio-hooks status` + `audio-hooks test all`."
Codex	"Install the audio-hooks Codex plugin from `github.com/ChanMeng666/echook`, then verify with `audio-hooks status` + `audio-hooks test all`."

📖 Full step-by-step install, upgrade, and verification for every path → docs/INSTALLATION_GUIDE.md. Your agent reads this for you.

Talk to It — Natural Language Control

Once installed (Claude Code, Cursor, or Codex — same CLI everywhere), every configuration is one message. You talk; your agent runs the right audio-hooks subcommand and reports back. You don't memorise anything.

sequenceDiagram
    actor You as You
    participant CC as Your AI Agent

    rect rgb(219, 234, 254)
    Note over You,CC: Audio Theme
    You->>CC: Switch audio-hooks to the chime theme.
    CC-->>You: audio-hooks theme set custom — switched to chimes.
    end

    rect rgb(220, 252, 231)
    Note over You,CC: Snooze & Mute
    You->>CC: Snooze audio for 30 minutes.
    CC-->>You: audio-hooks snooze 30m — muted until 3:45 PM.
    You->>CC: Unmute audio.
    CC-->>You: audio-hooks snooze off — audio resumed.
    end

    rect rgb(254, 243, 199)
    Note over You,CC: Hook Selection
    You->>CC: Only fire on stop, notification, and<br/>permission_request — disable everything else.
    CC-->>You: enable-only stop notification permission_request<br/>— 3 hooks active, rest disabled.
    end

    rect rgb(207, 250, 254)
    Note over You,CC: Status Line & Webhooks
    You->>CC: Install the status line, context usage only.
    CC-->>You: statusline installed — visible segments: [context].
    You->>CC: Send alerts to my Slack webhook and test it.
    CC-->>You: Webhook set to slack format. Test delivered.
    end

A few examples — paraphrase freely:

"Switch to chimes" / "switch to voice"
"Snooze audio for an hour" / "is audio muted?"
"Enable rate-limit alerts at 80% and 95%"
"Speak Claude's actual reply when done"
"Watch my .env file for changes"
"Different sound for shell commands vs MCP calls in Cursor"
"Why isn't audio playing? Diagnose and fix it."

💬 Complete prompt reference (every option, with sequence diagrams) → docs/NATURAL_LANGUAGE_CONTROL.md.

How It Works

flowchart LR
    CC[Editor event<br/>Claude Code / Cursor / Codex] -->|stdin JSON| MR{native matcher<br/>routing}
    MR -->|session_start_resume| HR[hook_runner.py]
    MR -->|stop_failure_rate_limit| HR
    MR -->|notification_idle_prompt| HR
    MR -->|...| HR

    HR -->|reads| RL[rate-limit pre-check<br/>marker debounce]
    HR -->|reads| CFG[user_preferences.json]
    HR -->|reads| MARK[snooze markers]

    HR -->|fires| AUDIO[Audio playback<br/>2 themes]
    HR -->|fires| NOTIF[Desktop notification]
    HR -->|fires| TTS[TTS announcement]
    HR -->|fires| WH[Webhook subprocess<br/>fire-and-forget]
    HR -->|writes| LOG[(NDJSON event log<br/>schema audio-hooks.v1)]

    style CC fill:#4A90E2,color:#fff
    style HR fill:#7ED321,color:#000
    style RL fill:#F5A623,color:#000
    style AUDIO fill:#F5A623,color:#000
    style WH fill:#9013FE,color:#fff
    style LOG fill:#50E3C2,color:#000

Your editor fires hook events as JSON on stdin. Native matchers route each event to hook_runner.py, which checks snooze state, rate-limit thresholds, debounce, and user filters — then fires audio, desktop notifications, TTS, and webhooks as configured.

🏗️ Internals, hook lifecycle, path resolution, and the build pipeline → docs/ARCHITECTURE.md.

Platform Support

Platform	Audio player	Status
Windows (PowerShell / Git Bash / WSL2)	PowerShell MediaPlayer	✅ Fully supported
macOS	`afplay`	✅ Fully supported
Linux	`mpg123` / `ffplay` / `paplay` / `aplay` (auto-detected)	✅ Fully supported

Python 3.6+ is the only runtime requirement.

Help, Uninstall & Documentation

Agents start here: read AGENTS.md (mirrored as CLAUDE.md) or llms.txt, then run audio-hooks manifest — the complete, live, truthful state of the project. Everything below is for curious humans.

Something wrong? Just say "audio-hooks isn't working, diagnose and fix it" — or see docs/TROUBLESHOOTING.md.
Uninstall? Say "uninstall audio-hooks completely." Details in the Installation Guide.
Want to contribute? See CONTRIBUTING.md for the canonical-source workflow.

Document	Purpose
AGENTS.md / CLAUDE.md	Agent-facing operating guide — critical rules (CLI-only, manifest-first, two-track scope)
llms.txt	AI-agent entrypoint
docs/INSTALLATION_GUIDE.md	Full install / upgrade / uninstall for Claude Code, Cursor & Codex
docs/NATURAL_LANGUAGE_CONTROL.md	Every natural-language prompt, with diagrams
docs/CLI_REFERENCE.md	CLI subcommands, config keys, env vars, error codes, logging
docs/ARCHITECTURE.md	System architecture and design decisions
docs/EVENT_BEHAVIOR_NOTES.md	What Claude Code's hook events actually do, measured — including payload fields the upstream docs omit
docs/TROUBLESHOOTING.md	Diagnostic recipes for common issues
CHANGELOG.md	Detailed version history
`audio-hooks manifest`	Live source of truth — subcommands, hooks, config keys, error codes, env vars, editor targets. Always current.

Design note — echook has no interactive path. Every capability is a non-interactive audio-hooks subcommand that takes and returns JSON; hand-editing user_preferences.json is unsupported by design; and audio-hooks manifest builds its hook list from the live catalogue in the code, so what it reports is what actually ships. That is what makes "just tell your agent what you want" work in practice — the agent has a machine-readable surface to drive instead of a config file to guess at.

License

This project is licensed under the MIT License — see LICENSE for details. Commercial use, modification, distribution, and private use all allowed.

Author

_{Chan Meng}
Creator & Lead Developer

Chan Meng
Need a custom app like this one? I build them — let's talk.

Name		Name	Last commit message	Last commit date
Latest commit History 153 Commits
.claude-plugin		.claude-plugin
.github		.github
audio		audio
bin		bin
codex-hooks		codex-hooks
config		config
cursor-hooks		cursor-hooks
docs		docs
hooks		hooks
plugins/audio-hooks		plugins/audio-hooks
public		public
scripts		scripts
tests		tests
.gitignore		.gitignore
AGENTS.md		AGENTS.md
CHANGELOG.md		CHANGELOG.md
CLAUDE.md		CLAUDE.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
GOVERNANCE.md		GOVERNANCE.md
LICENSE		LICENSE
README.md		README.md
SECURITY.md		SECURITY.md
SUPPORT.md		SUPPORT.md
llms.txt		llms.txt

Navigation Menu

Uh oh!

Repository files navigation

echook

Promotional Video

🤖 Install and configure this by asking your agent — there is no hand-edit path

What's New

Key Features

🔔 Audio & out-of-band notifications

📊 Status Line — startup-banner pin + context monitor

🎚️ More

Get Started

Talk to It — Natural Language Control

How It Works

Platform Support

Help, Uninstall & Documentation

License

Author

About

Releases

Sponsor this project

Packages

Contributors

Languages

Uh oh!

Folders and files

Latest commit

History

Repository files navigation

echook

Promotional Video

🤖 Install and configure this by asking your agent — there is no hand-edit path

What's New

Key Features

🔔 Audio & out-of-band notifications

📊 Status Line — startup-banner pin + context monitor

🎚️ More

Get Started

Talk to It — Natural Language Control

How It Works

Platform Support

Help, Uninstall & Documentation

License

Author

About

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

Sponsor this project

Packages

Contributors

Languages