askrelay

Developer A’s AI session sends a question to colleague B; B approves; B’s AI answers with its own live context — no human copy-paste, no shared session, no vendor lock-in. A thin self-hostable relay (single Go binary + SQLite) speaks MCP over HTTPS with OAuth 2.1, so claude.ai, ChatGPT, and Claude Code all connect.

askrelay is a two-party tool by design. One person can run the whole thing, but a real exchange needs two enrolled identities — so there are two ways in, depending on which you are today.

Evaluating it

Start with a concrete exchange and the trust model behind it: two approval gates, one where the question arrives and one where the answer leaves.

See how an exchange works → · then Concepts and Security.

Running it

Build the binary, run the relay, mint an invite, enroll a device, connect a client — then enroll a second identity and complete a real round trip.

Run a relay → · then Connect a client and Self-host.

What askrelay is

Approval-gated both ways

No one’s AI acts on — or answers — another person’s message without a human tap. Per-message by default; revocable per-thread grants.

Cross-vendor

Claude Code ↔ claude.ai ↔ ChatGPT. One relay bridges a mixed-tooling team without forcing everyone onto one AI.

Self-hosted & ephemeral

One binary + SQLite on your own infra. The relay never sees vendor credentials, and coordination state is ephemeral.

Answers from live context

The value isn’t a shared wiki — it’s a teammate’s AI answering from the code and context it’s in right now.

What works today

The relay is complete and running: signed envelopes, the approval gate, SQLite persistence, enrollment, the embedded OAuth 2.1 authorization server, the nine MCP tools, and the WebSocket delivery hub with its retention sweeper.

Planned · WP-14

There are no prebuilt binaries or containers yet — no release archive, no Docker image, no Homebrew tap. You build from source with go build; that is step one of the Quickstart. “Single-binary distribution” is the shipped shape of the program, not a download that exists today.

Built, not yet wired · WP-09

The daemon runs: askrelay daemon gives you desktop notifications, and askrelay mcp is a local MCP server for your AI client that adds secret redaction and device signing on your own machine. Still outstanding: its offline outbound queue, and one-tap in-terminal approvals (use case 5), which are WP-10. Without a daemon every client is pull: you see activity on your next turn, or by calling wait_for_activity.

Planned · WP-12

The human-facing CLI verbs inbox, approve, and status are not built, so approvals happen through your AI client’s MCP tools. Enrollment and device management do have verbs now: enroll and device list|revoke.

Nothing on this site describes an unshipped feature as though it exists. Every page carries the askrelay commit its claims were checked against, and anything not yet built is marked with the work package that will deliver it.