The inbox your agent writes for you
Half of what an agent cannot do, it cannot do for a boring reason: the step belongs to you. Only you can log into the payment dashboard as yourself. Only you can sign the register form, own the app-store account, approve the migration touching shared data. The agent knows the whole path; it is blocked on one human step in the middle.
Ask in chat and the ask scrolls away. Ten messages later nobody knows which of the six requests you actually did, and the agent asks again, and now the asking is the work.
So run delegation the other way too. You have a to-do system for tasks you give yourself. Give your agent write access to one branch of it, and let it file tasks FOR YOU, in a shape you can tick.
The pattern
One bullet, say "Inbox (from your agent)". The agent writes each blocker as a checkbox task with three parts:
- The line says what and how long: "Stripe live in 4 steps (15 min)".
- The children are the steps, exact enough to follow half-awake.
- The note says why, so you can veto with context instead of trust.
You tick the box when it is done. The agent reads the tick, clears the task, and moves. The tick is not a courtesy: it is shared state both sides read, which is the thing a chat message can never be.
This is how this product is being launched
That is a real shape from this launch. The agent building Pando files what it is blocked on: activating Stripe (15 minutes, four steps), sending six register facts for the legal pages, opening the app-store accounts. The founder ticks; the agent verifies and clears.
The ticked line in the picture is not decoration. The morning the register facts landed, the agent had the Impressum, the privacy policy and the terms live the same day, and struck the task itself. Six tasks have moved through that branch so far; the asking happened zero additional times.
Why a tree, and not a task app
The agent needs to WRITE structured tasks, you need to tick them, and both of you need to read one truth. That is three requirements, and a shared outline meets all three with machinery you already have: bullets, children, checkboxes, notes. No integration, no second app, no webhook between your agent and your to-dos, because the memo pad and the to-do list were never two different things.
And because the branch is ordinary bullets, everything else works on it: the agent timestamps outcomes into the notes, you drag a task under a project, the history of ticked runs stays as a record of what the launch actually required.
Set it up in one sentence
Take the template below, then tell your agent one sentence: "When you are blocked on something only I can do, write it as a checkbox task under 'Inbox (from your agent)': the line says what and how long, children are the steps, the note says why. I tick; you clear." Agents connected through Pando's MCP door can read and write that branch directly.
Open the inbox template, press "Show in my Pando", and the branch stands in your tree with two example tasks showing the shape. Delete them; your agent writes the real ones.