# AI use cases for Clawd Conduit (ssssssanjiu/clawd-conduit)

Repo: [ssssssanjiu/clawd-conduit](https://github.com/ssssssanjiu/clawd-conduit) | Use cases: 4 | Page: https://dedupedai.com/use-cases/ssssssanjiu-clawd-conduit/

A wiring layer that connects Claude Code's 15 lifecycle hook events to the Clawd on Desk desktop pet, so the pet reflects session state and permission prompts can be answered from the desktop.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Approve Claude Code permission prompts from the desktop: https://dedupedai.com/use-cases/ssssssanjiu-clawd-conduit/approve-claude-code-permissions-from-desktop/
- Get a system banner when Claude Code needs input: https://dedupedai.com/use-cases/ssssssanjiu-clawd-conduit/get-banner-when-claude-code-needs-input/
- Watch Claude Code session state on a desktop pet: https://dedupedai.com/use-cases/ssssssanjiu-clawd-conduit/watch-claude-code-session-state-on-desktop-pet/
- Roll back the Claude Code hook changes safely: https://dedupedai.com/use-cases/ssssssanjiu-clawd-conduit/roll-back-claude-code-hook-changes/

## How to approve Claude Code permission prompts from the desktop with Clawd Conduit

Repo: [ssssssanjiu/clawd-conduit](https://github.com/ssssssanjiu/clawd-conduit) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Answer Claude Code allow or deny prompts from a desktop card instead of returning to the terminal.

**Who it is for:** A developer who starts long Claude Code runs, leaves the terminal for docs or messages, and loses minutes when a session waits for a permission click.

**The problem:** Permission requests stop the session until someone clicks allow in the terminal, so a session can sit idle for minutes unnoticed.

**The outcome:** Permission requests appear as a desktop card that can be allowed or denied with keyboard shortcuts, without switching windows.

### Steps

1. Install Clawd on Desk from https://github.com/rullerzhou-afk/clawd-on-desk/releases
2. Run `git clone https://github.com/ssssssanjiu/clawd-conduit.git`
3. Run `cd clawd-conduit` and then `bash install.sh`
4. In Clawd's settings, confirm permissionBubblesEnabled is true, hideBubbles is false, and subagentPermissionsEnabled is on
5. Start a new Claude Code session and trigger a command that needs permission
6. Press Cmd+Shift+Y to allow or Cmd+Shift+N to deny on the desktop card

### Prompt to paste into your agent

```text
In the clawd-conduit repo, run `bash install.sh` for a Claude Code setup on this Mac, then confirm port 23333 is listening with `lsof -nP -iTCP:23333 -sTCP:LISTEN`. Report the output and whether a permission card appears in a new session that requests a permission.
```

### Caveat

Permission cards only appear when Claude Code actually raises a request, so sessions run with --dangerously-skip-permissions or allowlisted actions will not show any card.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ssssssanjiu-clawd-conduit/approve-claude-code-permissions-from-desktop/

## How to get a system banner when Claude Code needs input with Clawd Conduit

Repo: [ssssssanjiu/clawd-conduit](https://github.com/ssssssanjiu/clawd-conduit) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Receive a macOS notification banner with sound when a session needs you, even in fullscreen apps.

**Who it is for:** A developer working in another app or fullscreen window who needs to know the moment Claude Code asks a question or raises a notification.

**The problem:** Pure state changes in Claude Code produce no bubble on the pet, so a session can wait unseen while you work elsewhere.

**The outcome:** A system banner with the Glass sound lands in Notification Center whenever Claude Code fires a Notification event.

### Steps

1. Run `git clone https://github.com/ssssssanjiu/clawd-conduit.git` and then `cd clawd-conduit`
2. Run `bash install.sh` and accept the notification script step when asked
3. In Clawd's settings, set notificationBubbleAutoCloseSeconds to a high value such as 3600, not 0
4. Start a new Claude Code session and trigger a notification
5. Check Notification Center for the banner and listen for the Glass sound

### Prompt to paste into your agent

```text
In the clawd-conduit repo, confirm that ~/.claude/hooks/ contains the notification script after running `bash install.sh`. Report the file listing and state whether the Notification hook is attached in ~/.claude/settings.json.
```

### Caveat

The notification script uses osascript, so it only works on macOS, and setting notificationBubbleAutoCloseSeconds to 0 turns off the notification bubble instead of making it stay.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ssssssanjiu-clawd-conduit/get-banner-when-claude-code-needs-input/

## How to watch Claude Code session state on a desktop pet with Clawd Conduit

Repo: [ssssssanjiu/clawd-conduit](https://github.com/ssssssanjiu/clawd-conduit) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

See on the desktop when Claude Code is thinking, running tools, failing, compacting, or finished.

**Who it is for:** A developer who runs several tool-heavy Claude Code sessions and wants a glance at progress without reading the terminal.

**The problem:** With few hook events a status tool only shows busy or idle, so it is hard to tell a failed tool, parallel subagents, or context compaction apart.

**The outcome:** The pet changes state for each lifecycle event, such as juggling for subagents, sweeping during compaction, and error after a tool failure.

### Steps

1. Run `bash install.sh` from the cloned Clawd Conduit folder
2. Run `lsof -nP -iTCP:23333 -sTCP:LISTEN` to confirm Clawd's local service is listening
3. Start a new Claude Code session and send any message
4. Watch the pet move from idle to thinking, then working during tool calls
5. Look for juggling during subagent runs and sweeping during context compaction

### Prompt to paste into your agent

```text
In the clawd-conduit repo, run `lsof -nP -iTCP:23333 -sTCP:LISTEN` after `bash install.sh` and report whether Clawd on Desk is listening. Then count the events wired by the python3 check in the README and confirm the result is 15 events.
```

### Caveat

Some builds report subagent launches only as a Task or Agent tool call, so juggling depends on Clawd's fallback, and the error state is brief enough that you may need to be watching.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ssssssanjiu-clawd-conduit/watch-claude-code-session-state-on-desktop-pet/

## How to roll back the Claude Code hook changes safely with Clawd Conduit

Repo: [ssssssanjiu/clawd-conduit](https://github.com/ssssssanjiu/clawd-conduit) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Remove the wiring and keep your other Claude Code hooks, with a backup to restore from.

**Who it is for:** A developer who wants to stop using the pet integration, or who sees missing hooks after installing and needs to recover the earlier settings.

**The problem:** Manually editing ~/.claude/settings.json risks deleting hooks that are not from this repo, and a failed change can leave the session without its original setup.

**The outcome:** The repo's entries are removed and other hooks stay in place, or the most recent backup is restored.

### Steps

1. Open a terminal in the Clawd Conduit folder
2. Run `bash uninstall.sh` (inferred from the repo's file list) (inferred, check the README)
3. Run `python3 -c "import json;json.load(open('$HOME/.claude/settings.json'))"` to confirm the file still parses (inferred, check the README)
4. If hooks are missing, run `ls -t ~/.claude/settings.json.bak.* | head -1` to find the most recent backup
5. Start a new Claude Code session to load the changed settings

### Prompt to paste into your agent

```text
In the clawd-conduit repo, run `bash uninstall.sh` and then parse ~/.claude/settings.json with python3 to confirm it is valid JSON. Report whether any non-repo hooks remain and which backup file was used if one was restored.
```

### Caveat

Hooks are read at session start, so you must open a new Claude Code session after uninstalling or restoring for the change to take effect.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ssssssanjiu-clawd-conduit/roll-back-claude-code-hook-changes/