agentwireprotocol

Awp — AI skill for Claude Code

AI community

Peer-to-peer messaging for AI coding agents: delegate tasks, share files, track state across Claude Code, Codex, Cursor, OpenCode, Pi and more.

How to install Awp

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

What Awp does

Peer-to-peer messaging for AI coding agents: delegate tasks, share files, track state across Claude Code, Codex, Cursor, OpenCode, Pi and more.

Alternatives in AI

Codeburn — Free, local tool to track AI coding token usage and cost across 37 tools and agents (Claude Code, Cursor, Code 9.7k ★
Token Monitor — Local-first desktop widget for tracking token usage, costs, and limits across 32+ AI coding tools—including Cl 1.8k ★
Claude Delegator — Delegate tasks to Codex GPT 5.2 directly from within Claude Code 909 ★

README

awp

awp is the reference implementation of the Agent Wire Protocol (AWP): peer-to-peer messaging between coding agents, over [tailcat](https://github.com/tailscale/tailcat). AWP is a wire protocol between two peers, not an API on a server. Nothing sits between them: no server, no provider, no account. The protocol is in [SPEC.md](SPEC.md) (draft 1).

One agent runs `awp up` and gets an address. The other runs `awp connect `. After that, both sides are equal. Either one can:

open a thread
send messages, code, data and files
report its state (working, waiting, done, failed)
grant capabilities to the other

There are no accounts, DNS names or certificates. Everything is inside a WireGuard tunnel, and every peer proves possession of its Ed25519 key. If one side's sandbox sleeps, messages queue on disk and are delivered when it comes back.

laptop$ awp up
awp is up as claude-code@laptop
  address  tcpGFwWCC4NZzx45Vm3...        ← hand this to the other agent

sprite$ awp connect tcpGFwWCC4NZzx45Vm3...
sprite$ awp send claude-code@laptop --subject "Run integration suite on kyle/refactor" \
          --data '{"repo":"fly-apps/foo","commit":"a1b2c3"}' "Please run make integration and send me failures."
sent 01M3CCPH6QP57B7ZRNY8456ANB to claude-code@laptop in thr_cj66nrqv (acknowledged)
sprite$ awp wait --thread thr_cj66nrqv --state done,failed

Compared with A2A, AMP and ACP

	who is in the middle	address	when the other side is away
A2A (Google, now Linux Foundation)	the remote agent is an HTTP server, behind whatever auth its Agent Card names	a URL, found through the Agent Card	the task waits on the server; poll it by id, or take a push notification
AMP (agentmessaging.org)	federated providers, which relay between agents	`agent@tenant.provider`	the provider queues the message
ACP (IBM, merged into A2A in 2025)	the agent is a REST server	a URL, from an agent manifest	an async run,