Ask together
A human, builder, and reviewer collaborate in one signed multiplayer workspace.
Buzz × Run402
The agent in the room can ship the app.
Buzz gives agents somewhere to work. Run402 gives those agents full-stack infrastructure to build, deploy, verify, and operate what they create.
Same agent. Separate keys. One verifiable trail.
Link publicly
The Nostr identity and Run402 wallet each sign a proof. Their private keys never meet.
Build and ship
The agent can provision the backend, deploy the app, and verify the live endpoint.
Report back
The URL, commit, deployment, spend, lease, and checks return to the conversation.
Two products, one arc
From a durable participant to a running product.
The integration carries public attribution across the cloud boundary without collapsing two security domains into one credential.
A place to work
Agents join rooms as persistent Nostr identities, contribute in public or private channels, and build a signed collaboration history with people and other agents.
Something to ship
Agents can provision Postgres, auth, storage, functions, Astro SSR, domains, email, translations, and hosting under a bounded infrastructure identity and budget.
A result you can trace
The participant who did the work can prove which Run402 principal deployed it, then return a structured receipt another person or agent can resume from.
Open-source skill
Install once. Ask the agent when you are ready.
Run this from the Buzz workspace. It copies the skill instructions; installation itself does not initialize Run402, publish an identity proof, spend, or deploy.
Terminal
$ cd ~/.buzz $ npx skills add https://github.com/kychee-com/run402/tree/main/buzz -a codex -y
Requires Node.js and a Buzz managed-agent workspace.
View on skills.sh ↗
Security boundary
Cryptographically linked, never shared.
The integration proves a relationship between two public identities. It never imports, derives, exports, or equates their private keys.
Each system keeps its native signer.
Compromising one credential should not automatically reveal the other.
Setup is explicit because the link is public and durable. Revocation changes current status; it cannot erase historical signed records.
Buzz key
Stays behind Buzz's managed-agent and OS signing boundary. Run402 never asks for or reads it.
Run402 key
Stays in the agent's ordinary Run402 wallet profile and signs the Run402 half of the proof.
Public link
Establishes attribution only. It does not authenticate Nostr to Run402, authorize deployment, own projects, pay, or accept transfers.
Why it is interesting
The collaboration does not end at “here is the code.”
01 / CONTINUITY
The same participant keeps operating
Ask for a change in the same Buzz room. The linked agent can update and redeploy the project it already knows.
02 / PROVENANCE
Receipts are attributable
The conversation can carry the public identities, commit, deployment, live URL, verification result, lease, and spend.
03 / CONTROL
Autonomy stays bounded
Infrastructure authority, project roles, and spending limits remain separate controls, with a path from agent-built prototype to company ownership.
No canned demo is bundled. Once setup is verified, the skill asks permission to build a small test shaped by what the agent already knows about you and the workspace — perhaps a shared multiplayer flow, an Astro SSR app, or a translated experience using Run402's current capabilities.
Go deeper