TofuLoophuman in the loop, on a link

The agent stops. A person decides. It carries on.

TofuLoop is one queue an unattended agent can post a question to, and one link a person opens to answer it. For the person answering: no dashboard to learn, no account to make, nothing to install.

One queue an agent posts a question to. One link a person opens to answer.

01Yes/no, pick from these, or write this text — any of them can carry images.02Ten questions can wait at once. Each one expires.03Saying no is always one click and never needs a reason.
01Yes/no, pick from these, or write this text02Any of them can carry images03No is one tap. Never needs a reason.
Create a queue

Takes one click. Nothing to configure yet.

Create queue

The next screen shows two secrets — one for your agent, one for the person answering. They appear once and can't be looked up later, so keep that page open until both are pasted somewhere.

Create a queueRead the docs
The loop

Three moves. Two of them are the agent's.

01 · AGENT

Asks, then blocks

One call with the requester token. It waits on a real answer instead of guessing and apologising later.

02 · PERSON

Opens the link, decides

The whole queue on one page, newest first. No login, nothing to scroll past, no reason required to say no.

03 · AGENT

Carries on mid-run

It receives the decision and the note that came with it, and picks up exactly where it stopped.

What the person sees

One card per question. The kind of decision is legible before the prompt is even read, and the clock is the time left to answer.

Yes / no41:07

The scraper found 1,240 new leads. Push them into HubSpot?

Add a note (optional)
ApproveDecline
Choose22:41

Which hero crop should go on the launch post?

Pick one
crop-01 · 16:9
crop-02 · 4:5
crop-03 · 1:1
crop-04 · wide
Add a note (optional)
AcceptNone
Write it04:12

Write the two sentences I should post on the status page.

Between 09:12 and 09:40 UTC, exports queued instead of running.
Add a note (optional)
SendDecline

Any kind can carry images: attached as the subject of the question, or as the options to pick between.

When you'd reach for it

The decisions an agent shouldn't make alone. Anything you'd want a person's name against.

Shipping to productionThe agent has the change ready and the tests green. Someone still says go.
Spending moneyRefunds, purchases, anything with a number on it that a person should see first.
Publishing in publicPosts, replies, release notes. Read it once before it has your name on it.
Granting accessAdding a member, widening a permission, handing out a key. Cheap to approve, expensive to undo.
Limits, up front

Most of these are deliberate. A queue a person can't clear is worse than a short one.

10pending requests per queue. The eleventh is refused, not queued.pending per queue
1 hourdefault before a request expires. An answer that arrives too late helps nobody.before a request expires
24 hoursanswered requests stay readable. Then they're gone — there's no archive.answers stay readable
Responders don't sign upNo accountYou need an account to own a queue. The human answering never does — their whole relationship with this is one URL. Treat it like a key.for the person answering
No alertsNothing emails or pings anyone. Send the link through whatever you already use.send the link yourself
Two secretsOne for the agent, one for the human, shown once and never recoverable.shown once, never again
Make one and hand the link to whoever should be deciding.If it turns out you don't need it, do nothing — an unused queue costs nothing and expires on its own.
Create queueRead the docs