pi-clawd

Clawd on Desk integration for the pi coding agent.

This extension sends pi's session and agent lifecycle events directly to Clawd's local HTTP server, so your desktop pet reacts to pi work in real time — no hooks or external files required.

Requirements

• Clawd on Desk running locally
• pi coding agent

Installation

This extension is part of the pi-ext pack.

Via pi install (recommended)

pi install git:github.com/joel611/pi-ext

Run pi list to verify, then restart pi or run /reload.

Manual (copy)

Copy or symlink this directory into your pi extensions folder:

# Global
mkdir -p ~/.pi/agent/extensions
cp -r extensions/pi-clawd ~/.pi/agent/extensions/

# Or project-local
mkdir -p .pi/extensions
cp -r extensions/pi-clawd .pi/extensions/

Then reload pi with /reload or restart.

Usage

The extension auto-discovers Clawd on ports 23333–23337 and starts reporting immediately.

| Command | Description | |---------|-------------| | /clawd | Show connection status | | /clawd on | Enable state reporting | | /clawd off | Disable state reporting |

Event Mapping

| pi Event | Clawd State | Notes | |----------|-------------|-------| | session_start | idle | — | | input / agent_start | thinking | User sent a prompt | | turn_start | thinking | New LLM turn | | tool_execution_start | working | Includes tool_name | | tool_execution_end | working | Includes tool_name | | tool_result (error) | error | — | | agent_end | attention | If tools were used this turn | | agent_end | idle | If no tools were used | | session_shutdown | sleeping | — |

How it works

1. On session_start, the extension probes 127.0.0.1:23333–23337 to find Clawd.
2. Each lifecycle event is translated into a Clawd state payload and sent via POST /state.
3. If the port changes (e.g. Clawd restarted), the extension rediscovers automatically.
4. The extension identifies itself with agent_id: "pi" so Clawd tracks it as a separate session.

Troubleshooting

• "Clawd not running": Make sure Clawd on Desk is launched. The extension silently skips reporting when Clawd is unavailable.
• Pet not reacting: Check that the pi agent is enabled in Clawd's Settings → Agents panel.
• Port conflicts: Clawd uses 23333–23337. Ensure nothing else is bound to those ports.