Claude Code for Warp

Why it's ranked here

The integration solves a narrow but genuine workflow problem: supervising long-running Claude Code sessions without watching the terminal. Structured event payloads, protocol negotiation, automated shell tests, and a legacy fallback show more care than a basic notification wrapper. Its value drops sharply outside Warp.

What's good

Notifications carry useful context, including truncated prompt and response text, permission details, project identity, and failure information. The plugin prevents duplicate completion alerts and negotiates a mutually supported protocol version. Older Warp clients still receive basic completion, startup, and idle notifications.

Tradeoffs

Warp, Claude Code, and jq are mandatory. Installation also requires restarting Claude Code or reloading plugins. Legacy clients receive fewer event types and no structured failure notification. Completion summaries depend on reading the local transcript after a short delay, so this mechanism relies on transcript availability and timing.

How to use it well

Use it when Claude Code runs inside Warp and you regularly switch to other work while agents execute. It fits unattended tasks that may finish, stall, fail, or request approval. Configure notification behavior in Warp, then let the hooks report attention points. It does not replace Claude Code, another terminal, or general agent orchestration.

Observed

License

MIT License

Primary language

Bash shell scripts

Install surface

Claude Code plugin marketplace with separate Warp and Oz support packages

Interface

Claude Code lifecycle hooks communicating with Warp through OSC 777 terminal escape sequences

Platform support

Warp terminal on macOS, Linux, or Windows

Runtime requirements

Warp terminal, Claude Code CLI, and jq

Testing

GitHub Actions discovers and runs shell tests under test directories