internal/

Package api defines the types exchanged between the awp daemon and its local clients over the control socket.

Package bootstrap wires awp into the agent harnesses installed on a machine, so the next session of each already knows how to message other agents.

Package control is the local API between the awp daemon and its clients (the CLI, the MCP server, harness hooks): newline-delimited JSON over a Unix socket that only the owning user can open.

Package daemon runs an awp node as a long-lived local service and serves the control API that the CLI, the MCP server and harness hooks use.

Package harness names the agent harness an awp agent runs in (Claude Code, Codex, ...), so dashboards can show which is which.

Package mcp serves awp as a Model Context Protocol server over stdio, for harnesses that prefer tools to shell commands (spec section 15).

Package node is the Agent Wire Protocol engine: it owns the identity key, the durable store, the listeners and every connection, and implements the handshake, resume, acks, blobs, grants and reconnection of SPEC.md.

Package render turns daemon events into text for people and models: the CLI, harness hooks and the MCP server all show messages the same way.

Package store persists an awp peer's state in SQLite: the outbox of unacked messages, the per-thread "last seen" ids that resume needs, a log of every message sent and received, thread state, blobs and grants.

Package transport provides the byte-stream bindings AWP runs over (SPEC.md section 4): tailcat, embedded as a library, plus plain TCP and Unix sockets for Fly 6PN, local use and tests.

Package version reports the implementation version (not the protocol version, which is wire.Version).

Package web serves the awp web dashboard: the page (built from web/ in the repository and embedded here) and a JSON and server-sent-events API over the local daemon's control socket.