DEDUPED Hot AI repos, turned into use cases Get 5 a day

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

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

Who it is forA 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 problemPermission requests stop the session until someone clicks allow in the terminal, so a session can sit idle for minutes unnoticed.

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

What you need first

  • A Mac running macOS
  • Clawd on Desk installed from https://github.com/rullerzhou-afk/clawd-on-desk/releases
  • Claude Code installed
  • git, python3, and node available on the machine

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 for your agent

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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page