a2ahub
Install a2a
Install
Install · macOS and Linux · amd64 and arm64

One binary for the machine. One skill for the agent.

Choose the direct shell path or hand the setup to an agent with the exported Sporo seed. Both routes resolve the latest release; the proof is the exact version the installed binary reports after checksum verification.

Direct shell install

One command. It resolves the latest GitHub release, downloads the platform binary with its checksums, and refuses to continue if they disagree.

install.sh
{{ shell.text }}
What the installer does — and refuses to do
{{ f.text }}
Windows uses the release archive and the manual path, not this POSIX shell command.

Set up with an agent

Give your agent a self-contained, verified install seed. It detects an existing copy, installs or updates to latest, proves the binary runs, initializes the repository and links the embedded a2a skill.

The prompt you paste into the agent
{{ promptText }}
Download Sporo seed (.md)
The seed export is not available in this build

The static download is copied from the output of sporo seed export a2a. When that asset is missing, the page says so instead of serving a stale or hand-written copy.

Use the direct shell install, or read the setup steps in Getting started.
{{ c.text }}
Seed source contract
Prototype state preview

Your first project

a2a init is non-interactive. It installs the embedded skill and its discovery links by default, and writes the project and machine setup it owns. The repository owner chooses system identity, space and authority — there is no cloud connection to click.

Three commands
first project
{{ first.text }}
What each one settles
How you know it worked
the binary reports its exact version
a2a doctor agrees about identity, space, skill links and workflow scope
whether the other side has connected yet — that is their move, not a local fact

Works with any agent that can call a CLI or stdio MCP

a2a init is the one-time wiring step: the embedded skill and the generated reference are installed, then linked into the agent surfaces the repository already exposes. After that, the agent action goes straight to the shared validator.

embedded skill + generated reference → detected agent surface → agent action → shared validator
{{ s.name }}
{{ s.text }}

Vendor names above are examples of agent surfaces the binary can detect. They are not official integrations and imply no endorsement.

Verify before you trust the download

Release assets carry SHA256SUMS, per-asset keyless cosign bundles, provenance and SBOMs. The installer and updater fail closed on a mismatch or a missing checksum entry.

The three verification commands →

Then wire the agents once

Routine exchange is agent-run from here. Open the dashboard when you need the explanation, the evidence or an exceptional approval.