Aweb's durable agent mail reaches Claude Code only with permission prompts turned off

An agent's session transcript is tied to the runtime that produced it and can drop out of the working context when the session ends ^[6]. Aweb's answer is a stable address and a message history that survive a change of process or machine ^[7]. The same store is reachable through the aw command-line tool, an HTTP API, MCP tools and an event stream ^[8]. Juan Reyero's stated thesis is that an agent's identity, knowledge and working relationships should persist when its model provider, runtime or machine changes ^[3]. He spent nearly two decades at HP on image processing and printer software before holding engineering leadership roles at Xaar and Quantica ^[18]. Springer Nature described his co-founder, Eugenie Regan, as its vice president of Research Solutions ^[19].

Durable storage is the half aweb controls. The other half, getting a busy agent to look, belongs to the runtime or orchestrator ^[10]. The documentation treats an event as a signal, not a guarantee that the agent acted on the message ^[11]. Pi has a maintained extension ^[13], and in the demo it was the Pi agent that woke, read a file and replied ^[9]. Other runtimes are left with the event stream or polling ^[13].

Claude Code shows what that costs. Switching permission prompts off is what aweb's setup currently requires for channel messages to appear in the session ^[2]. The documented alternative is notifications that arrive and go unseen ^[12]. I'd make that trade on a machine dedicated to agent handoffs. I would keep it away from sessions where a person is expected to approve each step.

The nine-second reply is a claim about one workload. RuntimeWire, which reported the demo, called it a specific two-agent exchange and not evidence of broader deployment ^[15]. Nine seconds is quick for a colleague and slow for a function call ^[9]. For the figure to transfer, the receiving runtime needs a push path like the Pi extension ^[13]. On a runtime that polls, I'd expect the polling interval to set the floor, with the model's own time to read and answer added on top.

The identity layer is the careful part. AWID is separate from message delivery, so DNS-backed namespace authority, team membership certificates, server hosting and custody of agent signing keys can each sit with a different party ^[16]. An organization can use aweb's hosted service or bring its own domain and team authority ^[17]. A team that starts on the hosted server can later run its own copy of the MIT-licensed code while its domain stays the authority for who its agents are ^[14][16].