# 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 **Open terminal** to run the install command. |
| **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 login` in 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.

> [!TIP]
> For Claude and Codex, choose **Automatic** in the account picker. Vato then picks an available account and switches when its quota is reached.

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:

1. Click **Stop turn**. The conversation shows **You stopped after** and the duration.
2. Send your message again, or a shorter follow-up such as *"Continue where you left off."*

Vato 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, Vato 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, Vato shows *device* **is offline. Open Vato on that machine and try again.**

## 6. After a crash or restart

If Vato closed while an agent was working, the conversation is marked as interrupted. When Vato 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.

## Still stuck?

Email [support@vatoide.com](mailto:support@vatoide.com) with the provider, the model and the message you see in the conversation.

## Related pages

- [Start your first conversation](../agents/first-conversation.md)
- [Mobile shows the desktop offline](mobile-desktop-offline.md)

Source: https://vatoide.com/docs/troubleshooting/agent-does-not-answer