Let your AI chats work on their own

What is the AIO Loop?

The AIO Loop lets the AI chats in your AIObox windows keep working without you pressing send at every step: they pass work to each other, carry on by themselves and call you only when they need you. It needs AkiMCP connected to your chats; the Start page installs it and Connect AkiMCP links it to each account.

What does a chat need to take part?

A chat in an AIObox window that is connected to AkiMCP. AkiMCP gives it the AIObox guide, which tells it to end every answer with one line that starts with NEXT:. You do not write that line. AIObox reads it and nothing else in the answer, so it never guesses. The five forms:

• NEXT: continue: there is a next step the chat can take now.
• NEXT: user <what to decide>: the chat waits for you.
• NEXT: send <handle>: the work now belongs to another window.
• NEXT: wait <handle>: the chat waits for another window.
• NEXT: done: nothing is left.

A window handle such as P3·W2 names the window a line points to.

How do chats pass work to each other?

While the loop runs, AIObox acts on that line in three ways:

• Relay: after NEXT: send P3·W2 check the fix, window P3·W2 receives one line, [auto] P2·W1 → you: check the fix. It reads the sender's chat for context and does its own part.
• Auto-continue: tick Keep this chat going by itself under the AIO Loop button in a window's panel. When that chat ends with NEXT: continue, AIObox sends [auto] continue, after the wait you set in Settings › AIO Loop. The panel counts the turns; at the last one it turns itself off for that chat and tells you. On Notion, the same tick also presses Continue when an answer stops on "Maximum duration exceeded".
• Wake-up: when an answer names no next step, that window's lead gets an [auto] line, so it can coordinate or leave it be. The lead is the window that started the loop unless you choose another: the full panel's Answers that name no next step go to list picks any window, or the window itself to lead its own team, so several teams can work at once. A handoff carries the choice to the new window.

NEXT: wait and NEXT: done start nothing. Every automatic line starts with [auto], so a chat can tell AIObox from you. A line waits its turn while the chat is busy or you have a draft in its box, and never mixes into your text. Hourly caps limit how many lines AIObox sends.

What does the Inbox do?

The Inbox tells you when a chat waits for you. When an answer ends with NEXT: user, you get a desktop notification, <handle> needs you, with what the chat asks you to decide, and that window's panel shows a gold needs you chip. The Inbox is always on, even when the loop is off, and it only reads: it never writes into a chat. Click the chip to put it away; writing in the chat or a new answer clears it too.

How do I start and stop it, and when does it stop by itself?

Press Start on the AIO Loop button at the top of the full panel in any window; Pause, Resume and Stop are one click each, and Stop never asks you to confirm. There is one loop for the whole app, so every window shows the same button. A line under it says how many windows the loop watches and how much time is left.

The loop stops by itself when its time is up, or when several sends in a row fail, and AIObox tells you with a desktop notification and the reason.

Settings › AIO Loop sets how long a Start runs, how many turns one chat keeps itself going and how long Auto-continue waits before each continue. The panel shows the moment the running loop ends, in your computer's time.

How is it different from Handoff?

Handoff moves one chat's job to a new window on another account when its account runs low or the provider keeps cutting its replies off. It does not need the loop. It is off until you turn it on in Settings, after a notice on provider terms that you confirm; AIObox checks no provider's terms. Once on, it starts by itself, unless you keep a window out with its Auto handoff switch or press Hand off now yourself, and the Handoffs page keeps a History of every handoff. The AIO Loop is about chats working together: passing work between windows and carrying on until they need you. Both need AkiMCP; handoffs are drawn step by step in How a window is named.