Agent does not answer
Get a stuck or silent agent working again, from provider sign-in problems to usage limits and restarts.
If you send a message and nothing happens, or the agent stops halfway, work through the checks below in order.
1. Check that the provider is connected
Each agent runs on your own account with its provider. If that account isn't ready, the conversation shows a panel titled provider is not ready, with a status for the provider:
| Status | What to do |
|---|---|
| Install | The provider's command-line tool is missing. Click Install automatically (Claude Code, Codex, Gemini), or Open terminal to run the install command yourself. If the automatic installation fails, the error appears under the button: check your connection and try again. |
| Login | You aren't signed in to the provider. Click Open terminal to run the sign-in command. |
| Unavailable | Read the detail under the row, then click Recheck providers. |
You can also open Settings → Providers. Each row shows Connected or Not connected.
2. Sign in to the provider again
Provider sign-ins can expire, or be revoked from the provider's side. Sign in again:
- Claude: Settings → Providers → Add account, or
claude auth loginin a terminal. - Codex: Add account with your ChatGPT account, or
codex login. - Cursor: paste a new key into Cursor API key, or run
cursor-agent login.
For Claude and Codex, the message field has an account picker. If an account there is marked Disconnected, the provider rejected it. Use the reconnect button next to it to sign in again.
3. Check your usage limits
When you reach a provider limit, the conversation shows Usage limit reached, with the kind of limit (for example 5-hour or weekly) and when it resets.
You can:
- Wait for the reset time shown on the card.
- Switch to another account in the account picker (Claude and Codex).
- Pick a model from another provider.
If you see This model is currently at capacity. Retry or choose another model., the provider is overloaded. Send your message again, or pick another model.
4. Stop the turn and send again
If the agent looks stuck:
- Click Stop turn. The conversation shows You stopped after and the duration.
- Send your message again, or a shorter follow-up such as "Continue where you left off."
Neoo also watches for agents that stay silent. If a turn shows no activity for about five minutes, and the agent isn't waiting for you, a command or a server, Neoo stops it and resumes it once on its own.
5. Check the computer running the agent
If the conversation runs on another computer, that computer must be online. When it isn't, Neoo shows device is offline. Open Neoo on that machine and try again.
6. After a crash or restart
If Neoo closed while an agent was working, the conversation is marked as interrupted. When Neoo starts again, it resumes personal conversations that were running on this computer on its own. Archived conversations and Team conversations are not resumed automatically.
If a conversation still doesn't resume, open it and send a new message.
The answer is missing after the window reloaded
Neoo keeps the end of every turn even when the window crashes or reloads while the agent is finishing. About two seconds after a turn succeeds, Neoo checks that its final answer was saved in the conversation and writes it itself if the window did not. Turns that ended just before Neoo closed are checked again at the next start.
If a conversation that was already open still shows an unfinished answer, reload it: close and reopen the conversation, or restart Neoo. Only the final answer and the end of the turn are restored; tool steps that ran while the window was down are not listed, and nothing the agent did is lost or run again. This applies to agents and bots that run on this computer.
7. The working folder was deleted
If a conversation's folder no longer exists, Neoo repairs it when you send your next message and shows a Working folder recovered note in the conversation:
| What was deleted | What Neoo does |
|---|---|
| A worktree Neoo created | Recreates it in the same place from its branch: the local branch, then the one pushed to origin, otherwise a new branch from its base. Uncommitted files can't be restored, and the setup script doesn't run again, so reinstall dependencies if you need them. |
| Any other folder | Continues in the conversation's repository or, if that's gone too, in the project it was opened from. This folder isn't isolated, and it may be a different project, so check the agent's first changes. |
Scheduled and unattended work, and Bots, never move to another folder. They only get a worktree Neoo created back.
If you see the error le dossier de travail de la conversation n'existe plus (the conversation's working folder no longer exists), Neoo found nowhere to continue, or the folder may come back because its drive or network share isn't available. Reconnect the drive, or choose another environment from the environment picker.
"La machine distante ne répond pas."
This message (the remote machine is not responding) means Neoo asked another computer, or your Neoo Cloud machine, for something and got no answer in time. It often shows at the top of a bot chat hosted on Neoo Cloud.
- Reading something (a bot's chat history, the list of bots, a bot's settings) is sent again automatically when the connection comes back, and once more if the first answer is late. In a bot chat, the message goes away by itself as soon as a later read works.
- Changing something (saving a setting, importing, sending) is never sent twice automatically, so it can't be applied twice. Check whether the change was made, then try again.
- If the message stays, check that the other computer is on and signed in, or that your Neoo Cloud machine is running.
Still stuck?
Email support@vatoide.com with the provider, the model and the message you see in the conversation.