ssssssanjiu

Clawd Conduit — Development skill for Claude Code

Development community

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

How to install Clawd Conduit

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ssssssanjiu/clawd-conduit and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Clawd Conduit does

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

Alternatives in Development

Skills — My personal directory of skills, straight from my .claude directory 8.8k ★
Contributing To Clawd Code — Thank you for your interest in contributing to Clawd Code 231 ★
Wp Phpstan Review — WordPress PHPStan review - validates phpstan config, baseline discipline, CI wiring, and WordPress-specific st 76 ★

README

clawd-conduit

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

[中文](./README.zh-CN.md) · macOS · MIT

Follow-up question card above the pet, in English

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](https://github.com/rullerzhou-afk/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