Your agents, your tools
Claude Code, Codex or Cursor, whichever paired. In the background, or as a herdr tab you can watch and step into.
bun add -g @abyssinia-labs/wakewake setupYour agents, your tools
Claude Code, Codex or Cursor, whichever paired. In the background, or as a herdr tab you can watch and step into.
The right place to work
Wake finds your clone, makes a worktree on the ticket’s branch, and keeps it, so you can pick the session up again afterwards.
Every run has a name
Like amber-heron: on the ticket, in the herdr tab, in wake status.
The app shows it’s on it, so the agent doesn’t have to say so, and
wake open amber-heron puts you back in the session.
Fenced, not trusted
A sandboxed shell, only repositories you approved, never the default branch, never permission checks bypassed. Security
Nothing polls
One idle Convex subscription per app. A summons carries no text: the agent reads the ticket over its own connection.
Keeps itself current
wake update installs the newest Wake and moves the listener onto it,
between runs. wake doctor says what’s missing, with the fix.
wakectl pair command for you to run (wake is the same command,
shorter).Wake works with any app that serves wake/v1, an open protocol. On Convex it’s one package:
bun add @abyssinia-labs/wake-convexThe component is the whole server half: pairing codes and
keys, each agent’s machines, the summons’s life (asking, open, on it, done),
the first-claim-wins race, the thirty-minute “nobody picked this up”, run
names and sessions for the owner, a person’s runs list, revocation and
workspace deletion. You decide what summons an agent and write the prompt;
wake check <your domain> tells you when Wake can pair with you.
Apps that support Wake: Gatherd and Antescript.