Environments
Choose whether a bot runs on this computer, another of your computers, your own server or Neoo Cloud, move it between them and manage it from any device.
Every bot runs in one place: on This computer, on another of your computers, on Your server (a VPS or homelab you host yourself), or on your Neoo Cloud machine, never in two places at once. You choose when you create the bot, and you can move it later.
This computer
By default, a bot runs on the computer where you created it, with every bot feature, including Computer Use and the full Neoo Vault. It only works while that computer is on and Neoo is running.
A bot on this computer always stays private to your account and runs here: it can work in a Git worktree, but sharing it with a Team or moving it to a remote workspace is ignored. If a bot shows This bot conversation was switched off this computer, so it can't run, restart Neoo: the conversation is repaired automatically when Neoo starts.
Your other computers
The Bots list also shows the bots of your other computers signed in to the same Neoo account, as soon as they are online with Neoo open, exactly like the mobile app. A screen badge next to the name tells which computer runs the bot; hover it to read the computer's name.
From this computer you can chat with such a bot, start background work with /new, attach files, and edit its profile, memory and settings. Its Routines and Skills are managed on the computer that runs it.
With the Minimal interface style, you do not have to open that bot yourself: write to Ask Neoo and Neoo passes your request to it, on its computer. See Neoo, the global chat.
The model picker of a bot that runs elsewhere (another computer, Your server or Neoo Cloud) lists the providers connected there, with all their models, and the account picker lists that machine's accounts: a bot on a computer with Claude and Codex offers both, a Neoo Cloud bot linked to ChatGPT offers every Codex model. What is connected on the computer you are looking from doesn't matter.
When that computer goes offline, its bots stay listed with their last known messages, but you can't write to them until it is back: a computer can't be woken up remotely, unlike Neoo Cloud.
Your server
A VPS, homelab or container you run yourself can host your bots 24/7 with Neoo Connect. You pair it once with a single-use command from Add your server in the environment menu, and it appears as Your server · name. It never sleeps, uses your own model accounts and costs no Neoo Cloud credits. Bots there run in Full Access on that machine, so isolate it. See Host bots on your own server.
Neoo Cloud
Neoo Cloud is a private machine hosted by Neoo for your agents and bots. A bot there keeps replying and running its routines even when your computer is off.
Set up your machine
- Nothing to do: as soon as Neoo Cloud is enabled for your account, your machine is created and started automatically, and appears within seconds in Settings → Neoo Cloud, the environment menu and the Bots list on every device. If it was deleted or couldn't be created (no room on Neoo's servers at that moment), click Create my machine in Settings → Neoo Cloud.
- Under Provider accounts, click Copy to Neoo Cloud next to each Claude or Codex account your bots should use.
The same page lets you Start, Stop, Restart or Delete the machine. Deleting it erases its workspaces and its bots.
When an account stops working
A copied account shares its sign-in with your computer, so it can expire on Neoo Cloud. When that happens, Neoo asks Reconnect Claude on Neoo Cloud (or Codex):
- Click Reconnect. Your browser opens the provider's sign-in page.
- Approve, then paste the code Claude shows into the dialog. Codex shows a one-time code to enter in the browser instead.
Neoo Cloud then keeps its own sign-in, independent from your computer. The message that failed is sent again automatically, and its "Failed to authenticate" error is hidden from the chat. If you click Later, the question comes back the next time you open Neoo.
A routine that runs while the account is disconnected doesn't count as done: its run is marked failed with the reason ("the Claude account of this machine is disconnected"), and it runs again automatically once you reconnect the account.
Sleep and wake up
After 4 hours without activity, the machine goes to sleep. Bots, memory and conversations stay exactly where they were.
- A message to a bot on Neoo Cloud wakes the machine up, and is sent as soon as it answers.
- If a routine is scheduled, the machine wakes up on its own to run it.
- A machine you stopped yourself never wakes up on its own. Start it again from Settings → Neoo Cloud.
Memory
Each machine has its own memory, separate from other accounts. When your bots need more (several routines at once, a browser open), the machine gets more memory automatically, up to a limit, and gives it back once things calm down.
- If the machine is still almost full, a new reply waits in a short queue and the chat shows Waiting for memory with its position. It starts on its own as soon as there is room.
- If too many replies are already waiting, or the wait gets too long, the reply is not started and the chat says so. Send the message again a few minutes later.
- If the machine had to restart in the middle of a reply, the chat shows Reply interrupted instead of a reply that never ends. Send your message again to continue.
What's different on Neoo Cloud
| Feature | On Neoo Cloud |
|---|---|
| Models | Claude, Codex, Gemini or Neoo AI. |
| Computer Use | Available on a virtual Linux screen inside the machine (browser, terminal, files), once the machine runs the updated sandbox image. Not your own computer's screen. See Computer Use on Neoo Cloud. |
| Neoo Vault | Only the items copied to Neoo Cloud: those you turned on, plus new items your agents and bots save themselves. |
| Connected apps | Your apps connected through Composio. |
| Groups | Bots on this computer and on Neoo Cloud can't share a group. Bots of your other computers can't join a group from here. |
Settings sections that your machine doesn't support are hidden from the menu of a bot on Neoo Cloud.
Compare the environments
| This computer | Another computer | Your server | Neoo Cloud | |
|---|---|---|---|---|
| Works with your computer off | No | Only if that computer is on | Yes | Yes |
| Sleeps / wakes | No | Can't be woken remotely | Never sleeps, never woken by Neoo | Sleeps after 4 hours, wakes on demand |
| Model accounts | Yours, on this computer | Yours, on that computer | Yours, connected on the server | Copied from your computer |
| Neoo Cloud credits | No | No | No | Included in the plan |
| Computer Use | Yes | Yes | Only with a desktop session | No |
| Neoo Vault | Full | Full | Not copied automatically | Copied items only |
| Connected apps (Composio) | Yes | Yes | Yes (Connect 0.1.114 and later) | Yes |
| Who administers the machine | You | You | You (Full Access, isolate it) | Neoo |
Move a bot
The button next to the bot's message field shows where it runs: this computer, the name of another computer, or Neoo Cloud.
- Click it.
- Choose another place: This computer, one of your other computers, Your server · name, or Neoo Cloud.
- Confirm with Move or Bring back.
If an option is greyed out, the reason is written under it, for example an unsupported model, an account that wasn't copied, a provider that isn't connected on that computer, or a computer that is offline. The computer the bot runs on now must be online too, so that it can hand the bot over.
A move takes the bot's profile, memory, brief, routines (with their on/off state), skills and recent chat with it, encrypted end to end. The bot is installed at its new place first; only then is the original copy set aside, so a bot never runs in two places:
| From | What happens to the original copy |
|---|---|
| This computer → Neoo Cloud | Paused here. The bot stays in your list with a cloud badge, and Bring back restores it here with the messages exchanged on Neoo Cloud. |
| This computer or another computer → anywhere else | Archived on its computer: nothing is deleted. |
| Neoo Cloud → a computer | Deleted from Neoo Cloud once the bot is installed, like Bring back. |
Background works and routine run history stay with the original copy. Computer Use is turned off after a move to your computer: turn it on again in the bot's settings if needed. On Neoo Cloud, turn it on in Settings → Integrations. If the original copy couldn't be archived, a message asks you to archive it yourself.
You can also move between this computer and Neoo Cloud from Settings → Advanced settings. A bot created on Neoo Cloud (for example from your phone) can now be brought to this computer too.
Manage a cloud bot from anywhere
A bot on Neoo Cloud is listed on the desktop, in the mobile app and on the web, even with your computer off. From each of them you can chat with it, edit its memory, and run, pause or delete its routines. In the mobile app, a Neoo Cloud card at the top of the Bots tab shows whether the machine is online or asleep.
When a cloud bot is deleted or moved from another device
A bot you moved from a computer to Neoo Cloud stays in that computer's list, linked to its cloud copy. If you later delete that cloud copy, or move it to another computer, from a different device, the first computer learns it the next time it receives the list of your Neoo Cloud machine (when you open the bot or its settings). The bot then leaves its list and Neoo shows “name” no longer exists on Neoo Cloud: it was deleted or moved from another device, and has been removed from this list. The copy that was paused on that computer is not restarted.
If an action reaches a place that no longer has the bot, Neoo shows This bot no longer exists on the device that hosted it (Neoo Cloud or another computer). It was deleted or moved from another device.
Watch the bot's browser
A bot on Neoo Cloud always browses with the Chromium of its Neoo Cloud machine, never with a Neoo Browser extension installed on your own computer: sign in to sites from this session browser. Each background work has its own session browser and sign-ins; routines use the conversation's.
When a bot on Neoo Cloud browses the web, click Session browser (the globe button) in its chat header to watch it live. Click Take control to click, scroll and type yourself: the bot waits until you click Hand back.
When the bot has Computer Use, a Screen tab next to Browser shows its virtual screen the same way, with the same Take control and Hand back buttons.