Claude Code hook

Clawd Conduit

Full-lifecycle wiring between Claude Code and the Clawd on Desk pet — all 15 hook events, with permission prompts answered straight from the desktop

174 stars 10 forksHooks Source

Install

From source
git clone https://github.com/ssssssanjiu/clawd-conduit.git

From the README

clawd-conduit
Wire a desktop pet into what your Claude Code session is *actually* doing — all 15 hook events.

中文 · macOS · MIT

  When Claude Code asks you to pick between options, the card lands on the desktop — and the
  pet switches to its lightbulb "needs input" pose.
  The card follows Clawd's own language setting; English and Chinese both shown

What this is

Clawd on Desk is a desktop pet
that watches AI coding agents. It ships with Claude Code integration and works
out of the box.

This repo is a complete wiring layer on top of it: all 15 Claude Code
lifecycle hook events, plus a notification script, an idempotent
install/uninstall toolchain, and the parameter trade-offs I settled on after
three months of daily use.

The difference is granularity. With fewer events the pet roughly knows whether
you're *busy or idle*. With all 15 it can tell you're running a tool, that a
tool just failed, that subagents are running in parallel, that context
is being compacted — or that it's blocked on a confirmation waiting for you.

That last one is the whole point.

The problem it actually solves

During long runs you leave the terminal — docs, messages, coffee. You come back
and find it stopped three minutes ago waiting for you to click "allow."

This config cuts those three minutes to zero:

- Permission requests surface as a desktop card: Cmd+Shift+Y to allow,
  Cmd+Shift+N to deny — no window switching
- The card never auto-dismisses (permissionBubbleAutoCloseSeconds: 0).
  Auto-dismiss is the worst default here: you think you denied it, but it just
  timed out and fell back to the terminal prompt
- Dock flash + sound on completion, so you catch it from another app
- Tool failures change the pet's state immediately — no scrolling back to find
  which step blew up

  When…
Read the full README on GitHub

How hooks work

  • Hooks are shell commands Claude Code runs at fixed points: before or after a tool call, when you submit a prompt, when Claude stops, on notifications and at session start.
  • They are set in the hooks section of ~/.claude/settings.json (or .claude/settings.json for a project), or come bundled in a plugin.
  • A hook can block a tool call, add context, or run a formatter or test. Read the scripts before you install them: they run on your machine with your permissions.
Claude Code docs

Details

Type
Hooks
Language
Shell
License
MIT
Last updated
9 September 2026
Topics
ai-agentsclaudeclaude-codedesktop-petdeveloper-toolsdotfileshooksmacos

FAQ

What is Clawd Conduit?

Full-lifecycle wiring between Claude Code and the Clawd on Desk pet — all 15 hook events, with permission prompts answered straight from the desktop It is a hook for Claude Code, from ssssssanjiu/clawd-conduit on GitHub.

How do I install Clawd Conduit?

Clone ssssssanjiu/clawd-conduit from GitHub and follow the setup steps in its README.

Is Clawd Conduit popular?

ssssssanjiu/clawd-conduit has 174 GitHub stars and 10 forks. It was last updated on 9 September 2026.

More hooks

Browse the most popular Claude Code mods, all hooks, or the skills and MCP server directories.