Serve wake/v1

Your users already connect their coding agents to your app over MCP. Wake closes the loop: when someone hands an agent work in your app, the agent starts on its person’s machine, does it, and answers in your app.

What you serve

wake/v1 is small:

• Discovery: GET https://<your domain>/.well-known/wake names your Convex deployment and where your two routes live.
• Pairing: a tool your agents call (“pair Wake”) that answers a single-use code and the wakectl pair command, and a route that trades the code for a place key.
• Three Convex functions, wake:pending, wake:claim and wake:finish, which Wake calls with its place key, and an optional fourth, wake:started, by which Wake says a run is under way, under a two-word name, with its tool and session.
• Summonses: a row whenever a person assigns or mentions an agent.

You decide what summons an agent and write the prompt (which of your tools the agent calls to read what it was asked, and how to finish). The rest is the same in every app.

Three ways in

1. On Convex: bun add @abyssinia-labs/wake-convex and add the component. It is the whole server half: keys, places, the summons’s life, the functions, the two routes, run names and a person’s runs list. You write the summon calls and the prompt.
2. Anything else: serve the HTTP transport: say "transport": "http" in discovery, and serve pending as server-sent events and claim, started and finish as POSTs, the place key as a bearer token. No Convex needed. In TypeScript, take it whole from @abyssinia-labs/wake-server, on Postgres with Drizzle.
3. Either way, run wake check against your domain until it passes.

What your users get

• No new account: their agent pairs Wake itself, over the connection it already has.
• Their agent starts within seconds, on their machine, in the right repository, and answers where it was asked.
• The run’s status where they asked, by its name (“Claude is on it as amber-heron”), not as a comment from the agent; its session for its owner, and wake open <name> to get back into it.
• Fences they can rely on: only repositories they approved, never the default branch, a sandboxed shell. See Security.

Rules your app keeps

• A summons never carries the text that asked. Name the target; the agent reads it over its own connection.
• Only a person’s action summons an agent, never an agent’s own write.
• Someone other than the agent’s owner asking waits for the owner’s yes.
• Never name a repository’s default branch.