Conversation and background works
Talk to a bot in one ongoing conversation; long jobs run as background works that report back in the conversation.
A bot works like a colleague you message: you have one conversation with it, and it keeps track of everything. When you ask for something long, the bot doesn't keep you waiting: it starts a background work, keeps the conversation free, and comes back with the result.
One conversation
Every message you send goes to the bot's Conversation. There is no menu asking where to send it: press Enter (or the send button) and the bot gets it.
The conversation picks up where you left off, even days later: the bot keeps its provider session, and Neoo also keeps a journal of everything it did, so it can find past work again.
Background works
A work is a job that runs in the background, in its own session, while you keep talking to the bot. The conversation stays a conversation: a work never fills it with status cards. It shows up in three places, each with one role.
In the conversation: chips attached to messages
- When a work starts, a small chip is attached to the bot's message: {title} · started in the background. It appears under the bot's reply once its turn is done; while the bot is still working, the dock above the message box already shows the work, so it is not shown twice. Starting works doesn't split the bot's turn: its steps stay in one Worked for… block. A work you start yourself shows the same chip on your side of the conversation. Hover the chip to read what the work was asked to do and, for a bot on this computer, where it runs (the project folder, or no project from your personal folder). Click it to open the work.
- When a work finishes, the bot speaks again: a chip {title} · done in 3 min (or failed, stopped) followed by its short summary of the result (the key answer and figures). The complete result stays in the work; the chip opens it. The bot's time spent reading the result is not shown: there is no "Worked for…" line on that reply. You get one notification, for that reply: the work finishing, its result card and a failed work don't notify on their own. A bot reply that only starts or continues a work ("It's started") doesn't notify either; you hear from the bot when the result is back. A question from the bot or from the work still notifies right away. A work that asks you a question waits for your answer instead of finishing: it stays in Waiting for you, the bot does not ask the same question again in its own conversation, and your answer (from the work, For you, Neoo's chat or the phone) resumes that same work.
If you're talking to the bot when a work finishes, it replies once its current answer is done; if you've already written to it since the result arrived, it has read the result and doesn't post a separate reply. Work results are always posted right away, even when the bot's reports are grouped in a daily digest.
A work you start takes the first words of your request as its title. On the Neoo desktop app, a short title of a few words replaces it a moment later (for example "Invoice reading accuracy" instead of "In the Neo Accounting project, we launched…"), in the sidebar, in the Works menu and on the chips. A request that is already short keeps its own words. Works started before this change keep their title.
Above the message box: the dock
What is running lives in a dock right above the message box of the bot's conversation, and nowhere else in the conversation. Its header says In the background · {count}; click it to fold or unfold the list.
- A running work shows its title, how long it has been running (for example for 4 min) and Open.
- A routine running now shows its state and Open to follow its run.
The dock disappears when nothing runs. While you're in the conversation, the Works menu under the bot's name no longer repeats the running count: the dock already shows it.
Background tasks: what the bot left running
A bot can start a long command in the background (a test gate, a build, a watcher) or hand part of the job to a sub-agent, and reply before it ends, for example "The gate is still running, I'll pick up when it finishes." On the desktop, for a bot that runs on this computer, a strip right above the message box lists what is still running, in the bot's conversation and inside each work. Its header says Background tasks · {count}; click it to fold or unfold the list.
- Each task shows a short name (the useful part of the command, for example
bash scripts/verify.sh; hover it to read the full command), how long it has been running (for example for 8 min) and, when the command writes output, its last line. - {name} resumes as soon as they finish is added to the header when a bot on a Claude model has already replied and is only waiting for these tasks. You don't need to ask again: the bot is woken when a task ends and carries on.
- Waiting for 1 background task (or Waiting for {count} background tasks), with a clock, replaces Worked for… on the bot's last turn in the conversation for as long as that bot is only waiting. The bot has replied but is not done. You can still write to it. When it is woken the turn shows In progress for… again, and Worked for… once nothing is left running.
- Stop ends one task without stopping the bot. Click Stop, then Stop? within four seconds to confirm; after that the button goes back to Stop and nothing is stopped.
The strip disappears when nothing runs. A work that has replied but still waits for one of its background tasks is not finished: it stays in the dock and in the Works menu as running, and is listed as done only once the bot has reported back.
A work that needs you
A work that asks you something gets its own card, between the dock and the message box. It shows one request at a time, the oldest first, under the title of the work that asks:
- A question is shown in full: pick an option, or choose Other to type your answer. It goes to the work that asked, which carries on. Skip declines the question. A work's question stays open until you answer or skip it, even after the work's turn ends or Neoo restarts; your answer resumes the work. A question with a time limit (other agents than Claude) shows Expires in {time}.
- A permission, a connection or a secret shows A request is waiting for you: it is answered inside the work, and Answer opens it.
- Open opens the work, to read what it did before you answer.
When several works are waiting, the other requests are stacked behind the card (the top of each one sticks out with its title, two at most) and the header shows where you are, for example 1 of 3. Answering brings the oldest request left to the front. To answer in another order, click a stacked request: it comes to the front, and the one you were looking at goes back into the stack. The arrows next to the count (Previous request, Next request) do the same, one step at a time.
In Neoo's chat, this card also carries what your other Bots ask about the requests Neoo passed on to them: see Answering a Bot's question without leaving Neoo.
Since your last visit
On the desktop, when works finished while you were elsewhere, the dock also lists them under Since your last visit, with the time they finished. Show scrolls the conversation to the bot's summary of that work, Open opens the work, and Mark as read clears the list. A work that finishes while you're looking at the bot's conversation is not listed: its result arrives in front of you.
Start a work
Let Neoo sort it. Just write in the bot's conversation. Before the bot sees your message, Neoo sorts it, the same way it sorts the messages of the main Neoo chat:
- Any task (a ticket or suggestion number such as
#2490, a link, a diagnosis, a fix, a research, an audit…) starts a new work. Your message stays in the conversation, followed by the chip {title} · started in the background, and the conversation stays free. - A follow-up of one of the bot's works ("for the 2477 one, add a before/after screenshot", "how is it going?") goes to that work. The chip reads {title} · follow-up sent, and the work's new result comes back in the conversation.
- Everything else stays in the conversation: greetings, thanks, a quick question, a question about the bot itself, and your answer to a question the bot just asked (even "Yes, fix it and add a test"), because that context is in the conversation.
Short messages ("thanks", "ok") and answers to the bot's question are sorted instantly. Other messages are sorted by a small model on the bot's own account (Claude Haiku with a Claude account, GPT-6 Sol with a Codex account), which takes about 3 seconds. If sorting fails (offline, quota, no answer within 8 seconds), the message simply goes to the conversation.
When Neoo got it wrong, a button under your message fixes it in one click: Answer here instead (the work it started is stopped and archived, and the bot answers in the conversation), Make it a work (the bot's answer stops and a work starts), or Make it a new work after a follow-up. The button disappears when you send another message.
- Any task (a ticket or suggestion number such as
Run in background. Type your message and click the rocket button next to the send button, or press Alt+Enter. In the mobile app, touch and hold the send button and choose Run in background; on vatoide.com, the rocket button and Alt+Enter work as on the desktop. The main Neoo chat on the desktop has no rocket button: every message you send there goes through Neoo, which finds the Bot for it (see Neoo, the global chat), and Alt+Enter sends the message like Enter.
/new <message>. Type/newfollowed by the task. On the desktop, the command is marked above the message box./newalone opens an empty work where you write directly.
You can also choose Start a work in the Works menu under the bot's name: it prepares /new in the conversation's message box.
To give more instructions to a running or finished work, just write them in the conversation ("for the price audit, add Germany"): Neoo sends them to that work instead of starting a new one. You can also open the work and write in it.
The same request never starts two works. If the same bot receives the same request twice within two minutes (a double send, a second click, a message sent again after an error), the second one joins the work that is already running: no second chip, no second run. Different requests still start one work each, so three tasks sent in a row run in parallel. Sending the same request again after the work has reported, or with another model, starts a new work.
Follow your works
Under the bot's name, the Works menu lists every work. When a work is open, it also shows how many other works are running and a dot when one is waiting for you (in the conversation, the dock shows this). It lists:
- Conversation: back to the conversation.
- Waiting for you: works that asked you a question or a permission.
- In progress: works running now.
- Recent: finished works.
- Routines: one line per routine, its latest run.
When a work is open, ← Conversation next to its title brings you back.
The bot's avatar moves only where something is really running. Next to the bot's name at the top, and next to its messages, it moves while the open conversation or work is running and stays still once it is finished, even when the bot is busy with another work. The same goes for the lines of For you (Minimal style), which are never running work. Only the bot's avatar in the list of bots moves whenever any of its works runs. This works the same on desktop, mobile and the web app.
While it works, the bot steps back a little, turns its head and looks up, and three small bubbles in its color rise one after the other above it, then fade out together. On small avatars, such as the sidebar list, a single larger bubble appears beside its head instead, so it stays readable. The bot always stays whole. When the work ends, the bubbles fade out in half a second instead of stopping at once. With reduced motion turned on in your system settings, the avatar shows a still image of the bot with its three bubbles.
Routine runs are works too
Each time a routine runs, it gets its own work, named after the routine. Questions and permission requests the bot asks during the run appear there; the report card in the conversation links to it. While it runs, the routine also has a row in the dock.
A routine that runs often doesn't fill the list: each routine shows once, as its latest run, with the number of runs (for example Routine · 17 runs). With Only report what changed, a run with nothing new ends with NOTHING_TO_REPORT: no report in the conversation, and the run is archived when it finishes unless it waits for you or you wrote in it. Heartbeat checks that end with HEARTBEAT_OK are handled the same way.
In Settings → Works, the runs of a routine are grouped in one line. Click the line to unfold its runs; the routine's … menu has Archive runs.
Archive, mute or delete a work
| Action | What it does |
|---|---|
| Archive | Removes the work from the Works menu and the sidebar. It stays in Settings → Works; Unarchive puts it back. |
| Mute notifications | The work keeps running, but its questions and reports no longer notify you. |
| Delete | Deletes the work and its messages for good. For a work with messages, the first click turns Delete into a red Confirm. A work that is still running can't be deleted. |
These actions are in the This work section of the Works menu, in Settings → Works (the … button of each line) and, on the desktop sidebar, in the … menu of a work under its bot.
See all works
- Desktop: Settings → Works, or Works at the bottom of the Works menu. Works are sorted under Today, Yesterday, Previous 7 days and Older, with their state, the time of their last activity and the start of their last message. Show archived works shows or hides archived ones.
- Mobile and vatoide.com: open the menu under the bot's name and choose All works.
The Conversation can't be archived or deleted.
Restore a message in a work
On the desktop, open a user message's actions in a work of a bot running on this computer and choose Continue from this message. Neoo previews the agent file checkpoint, lists any files that will be deleted and asks for confirmation. It undoes this work's file changes from that point, removes later messages and reopens the prompt for editing.
Restore is unavailable while the work is running, waiting for an answer or has queued messages. The work's journal entries for the undone turns are removed too, so the bot doesn't believe it did work you just undid. Shared memory and external actions, such as sent emails, are not rolled back.
For bots on Neoo Cloud, the same actions are offered when the machine supports file restore (Connect and its Claude bridge up to date). Mobile and the web companion do not offer restore yet.
Changes the bot makes show in the conversation
When the bot changes its own setup during a conversation or a work, a small line records it, for example Routine created · Neoo IG — 5 random captions. This covers routines, actions, triggers, knowledge, skills, the brief, and its role, instructions and memory. The bot's internal notes (checkpoints, journal, working ledger) stay hidden.
Limits
- The Works menu lists the 30 most recent works and the 20 most recently active routines.
- Settings → Works shows every work on the desktop for bots on this computer; for Neoo Cloud bots, and on mobile and vatoide.com, the 100 most recent.
- Works can't be renamed yet.
- The same-request check runs on the computer that hosts the bot. Neoo Cloud bots don't have it yet.
- On a Neoo Cloud bot, a work keeps the model it had when it started; model and account changes apply to the conversation.
- A Neoo Cloud machine that hasn't been updated yet treats
/new <message>as a plain thread that opens right away, without a card or a report in the conversation. - In the mobile app and on vatoide.com, the dock lists running works and works waiting for you; a work's question is answered by opening the work. Since your last visit is desktop only.
- The Background tasks strip is on the desktop only, for bots that run on this computer. It is not shown for a bot on Neoo Cloud or on another computer, nor in the mobile app or on vatoide.com; there, a work that waits for a background task is still shown as running.
- Quitting Neoo stops the commands a bot left running in the background: after a restart the strip is empty.
- Neoo sorts the messages of bots that run on a computer of yours: on the desktop, and from the mobile app or vatoide.com when that computer receives them. Messages to a Neoo Cloud bot and to the main Neoo chat keep their own path, and so do messages written inside a work or a routine run,
/commands, replies to a specific message and the first message (the bot's mission). The one-click fix appears only on the desktop that runs the bot. - The "done in" duration is shown for the first result of a work, when its start is in the loaded part of the conversation; later results (after you or the bot add instructions) show done.