ayedesk
Get early access

How it works

Your agent asks. You decide. It carries on.

Ayedesk is a loop with four steps and no messenger. The agent never polls and you never go back to a chat window to say “approved”.

  1. The agent posts a card.

    When work needs your eyes, the agent posts a card: a title, what changed and where (branch and commit, or a link), up to twelve checks with how to test each one, and in one line what happens if you approve.

    Posting is safe to retry: the same request never makes a second card. A card on one change for iOS, Android and the web becomes a group, and a release card can promote it to production.

    The To validate lane: 8 cards and 3 sessions waiting. A critical card, #105 Pricing page copy, has 1 of 3 checks OK and 1 failed. If approved: publish the copy on the dev site.

  2. It waits, without spending tokens.

    The agent starts one command in the background and stops. Nothing runs in the conversation while you think: no polling loop, no tokens. The card shows Agent waiting, so you know which decisions unblock someone right now.

    When you decide, the command prints one line and exits, and that wakes the session up. In Claude Code this is a background command; in Codex the agent ends its turn and picks the decision up from its inbox.

  3. You tick and decide.

    Mark each check OK or failing, add a one-line note, then validate or send it back. From the Mac, the iPad or your phone. A decision becomes final after ten seconds, so a slip of the finger costs nothing.

    Approving allows exactly the action written on the card. Agents can never decide, undo or reopen: there is no tool for it, and the API refuses an agent that tries.

    A card in detail: four checks, each with how to test it and the expected result, ticked OK by Jordi, and the decision: approved, merge to dev and deploy.
    The decision bar: a comment field, required for changes; Changes requested; Send notes now, with one note; Validate.

  4. The agent wakes up and carries on.

    The session that was waiting claims your decision, once, with everything it needs: the outcome, your comment and each failed or flagged check. It answers every note in a line, Fixed: … or Not changed: because …, and goes on with exactly what the card said.

    If you asked for changes, it sends a new version of the same card, and the loop starts again where it left off.

    A work item conversation: the agent picked up Jordi's three comments, answered each one in a line and proposed splitting the work into two items, with Accept and Reject buttons for people only.

Revisions

A new version is the same card.

After feedback the agent resubmits the card, never a new one. Version 2 opens with what changed since you last looked and the agent's answer to each of your notes. Only changed or new checks need you again; the ones you passed are kept, marked from v1.

The card keeps every version, so the record shows how the work got to Validated.

Version 2 of a card: the failed check from v1 with the agent's reply, “Fixed: the clock now re-reads the time after a tab switch”, what changed in v2 (1 changed, 1 new), and the checks: one kept from v1, one changed and one new.

Evidence

See the proof, not a promise.

Agents attach screenshots and files to each check, and mark what matters in red. Open them full screen: zoom, pan, swipe across checks, and put version 1 beside version 2. Draw a box where something is wrong, add a note and fail the check with it; the agent gets your boxes with the decision.

The evidence viewer comparing v1 and v2 of a check, Card picker: open cards first, decided under them. In v1 the decided card #94 sits between open cards, marked in red by the agent; in v2 it sits under Decided.

When nobody was waiting

Decisions don't get lost.

Sessions end, laptops sleep. If no agent was waiting when you decided, the card says Nobody has picked this up, and the decision waits in the inbox.

  • Any session can pick it up

    Tell any agent session to check Ayedesk. It reads the inbox, claims what belongs to it and carries on.

  • Claimed exactly once

    A decision is claimed by one session. Another that tries is told it's taken and leaves it alone.

  • Resume after a crash

    A session that lost its wait runs the same command again and gets its decision back.

Give your agents a desk.

Free during early access. We're opening Ayedesk a few desks at a time.

Get early access See pricing