Queue, usage limits and agents working together

Queue messages that survive a restart, recover from a provider usage limit, compact long Claude conversations, and let agents read, message and organize the conversations of your project.

Queue messages during a turn

While an agent is working, you can type your next message and choose Add to queue. It is sent automatically when the current turn ends, even if you pressed Enter just as the turn was finishing. Queued messages appear above the message field.

If the conversation works in a worktree that was deleted in the meantime, Neoo recreates it from its branch when the queued message leaves, not while you queue it.

  • Move up and Move down change the order in which they leave.
  • Click a message to edit it, Steer to send it into the running turn now, or the cross to remove it.

The queue is saved on your computer. If Neoo closes or restarts, your queued messages are still there. To be safe, nothing is sent on its own after a restart: the queue shows Queue paused after Neoo restarted until you click Resume.

From the mobile app, you can also reorder the queue of a conversation running on your computer.

How automatic account selection picks an account

When a conversation uses automatic account selection, a new conversation starts on the account whose weekly quota would be lost soonest: the one with the most weekly usage left per hour before its weekly reset. For example, an account with 48% left that resets in 2 days goes before an account with 80% left that resets in 5 days. An account close to a limit (85% used or more in its 5-hour or weekly window) only goes first if every account is that busy.

A conversation keeps the account it started on for as long as that account answers, so the agent keeps its context.

When a provider usage limit is reached

If you linked several accounts of the same provider and the conversation uses automatic account selection, a limit on one account doesn't stop the work: Neoo continues the same turn on another available account. Nothing is shown in the conversation, and the turn keeps a single Worked for duration.

When every account is blocked, or the conversation is pinned to one account, the conversation stops and shows Limited in the sidebar. A banner above the message field tells you when the limit resets, if the provider says so. By default, Neoo continues the conversation by itself shortly after the reset time, and the banner shows Resumes automatically at that time.

  • Resume now: sends "Continue where you stopped." right away, for example after you add credit or switch account.
  • Cancel automatic resume stops the planned resume; Resume at reset plans it again. If you send a new message before the reset, the planned resume is cancelled.
  • Snooze until reset: moves the conversation out of your active list until the reset time, without resuming anything.

Messages waiting in the queue don't leave while the limit applies. The queue shows Queue paused by the usage limit and leaves again when the conversation resumes, or when you click Resume.

To choose yourself after each limit instead, go to Settings → General and set After a usage limit to Let me choose.

Return to a long Claude conversation

Claude keeps a conversation in a prompt cache for about an hour on a Claude subscription (5 minutes with an API key). When you come back later to a large Claude conversation (200,000 tokens or more by default), Claude has to read the whole history again at full price. Neoo then asks before sending your message:

  • Compact and continue: Claude summarizes the history first, then answers. The following messages use far fewer tokens.
  • Keep full history: your message is sent with the whole conversation, unchanged.
  • Don't ask again: keeps the full history and stops asking in this conversation.

The question appears in English, French or Dutch, following your response language. If you don't answer before the question expires, the full history is kept. Bots never ask: they keep the full history.

How Neoo keeps context small

To use fewer tokens, Neoo gives the agent its standing instructions once per conversation, in the system prompt, instead of repeating them in every message. Memories relevant to your request are added to the first message of a conversation, and again after the conversation is compacted; later, the agent searches your memories itself when it needs them.

Delegated tasks

An agent can split work into tasks that run in their own conversations. Their results return through a persistent internal inbox, without joining your message queue. Claude and Codex can receive them during an active turn; other providers resume when the conversation is free. Your queued messages, permission requests, stops and usage limits retain priority. A Delegated tasks finished card identifies the returned work.

In Workflows, open a task and click Open the task conversation to read the full conversation of that task.

Agents working across your conversations

Agents can see and act on the other conversations of the same project. They can:

  • list them and read their messages, including older parts of their own conversation;
  • rename a conversation;
  • send an internal message to another conversation. It is delivered to the agent with its source identified, without using your message queue or changing your draft;
  • pin, unpin, archive, restore, settle or mark a conversation as unread.

Agents never see conversations from other projects, Bots or Neoo Design this way. An agent can't send a message to a conversation that has more permissions than its own, and can't archive itself or a conversation that is still working. In Plan mode, agents can only read.

Next steps