AI Agents
Troubleshooting the Chat
What to do when the DevOps AI Agent chat does not open, the agent is stuck or asks for something, a server will not answer, or Resume Chat is missing
Before You Start
A chat problem has four places to look at: the deployment steps before the chat opens, the connection to the chat page, the agent’s own work on the server, and the state of the server itself. The server’s manage page shows its status and its Resume Chat button, so it is the place to look first. See The DevOps AI Agent for how the chat works.
An AI agent can be wrong. When it reports that something works, open the address yourself, and when it does something you did not want, press Stop before you ask it to undo anything.
Before the Chat Opens
The status page says ‘Deployment failed’
The status page stays on one stage
The form says that an AI-assisted deployment typically takes 5–15 minutes in all. If a stage is still showing after that time, open a support ticket and name the repository. The Cancel and return to Dashboard link only takes you to your dashboard; it does not stop the deployment.
The page says ‘Connection to deployment agent failed’
The message reads “The deployment interface could not be reached. This may be a temporary issue.” Press Retry Connection. If the chat still does not appear, go to the server’s manage page and press Resume Chat, which gives the chat a new link.
My repository is private
AI Deploy takes public GitHub repositories. For a private one, use your own agent with the AI Agent MCP: see Your Own Agent.
While the Agent Works
The agent asks me for a key or a password
It needs the value for a step, and it waits for your answer in the chat. Give it a key you can revoke, with only the permissions the application needs. See Safety and Control.
The agent seems slow
Installs and builds can take minutes, and a tool row with a running status icon means that a command is still going. Expand the row to see its arguments. If you want the agent to stop, press Stop.
The agent seems stuck
Press Stop, then write: “What are you trying to do, and what is failing?” Give it what it is missing, such as a setting, a key, or a decision. The agent is instructed to tell you plainly what it tried and what it needs when it cannot go on.
The agent said it finished, but the address does not open
Check that the server is Online on the manage page, then ask: “The address does not open. Check the web server, the application, and the certificate, and tell me what you find.” Open the address in a private window, so that a cached page cannot mislead you. See Ubuntu VPS for what the default domain is.
The agent did something I did not want
Press Stop. Expand its tool rows to see which commands it ran, and ask it to reverse the last change. If you took a snapshot first, restoring it undoes everything written since: read Restoring a Snapshot, because a restore also deletes the snapshots newer than the one you restore.
Coming Back to a Chat
Resume Chat is missing
Only a server that has a deployment chat shows the DevOps AI Agent card, and only while the chat’s status is active, completed, or ready. A server deployed from the Ubuntu VPS marketplace listing or through the API has no chat, and a chat cannot be started for a server you already have. See Where It Appears.
Resume Chat is disabled
While the server is paused for a low balance the button is disabled, and its tooltip reads “Add funds to resume”. Add funds and wait for the server to be running again: see Billing.
The agent says it cannot reach the server
Open the server’s manage page and look at the status.
- Paused or powered off. Power the server on, or add funds if it was paused for a low balance. See Managing VPS Apps.
- Online, but the root password no longer works. A password changed inside the server is not known to RepoCloud. Press Reset on the manage page, then Resume Chat.
- Online, but SSH is blocked by a firewall rule or an SSH setting. Open Console on the manage page opens the server’s serial console, which does not use the server’s network. See Safety and Control.
Getting Help
When these steps do not solve it, open a ticket at repocloud.io/support/new and include:
- the repository’s address and the name of the server
- what you asked the agent to do
- the agent’s last messages, or the text of the error you saw
A ticket is text only, so paste the text of the error and what the agent said. For problems that are not about the chat, see Troubleshooting.
Next Steps
Snapshots, Stop, and your own way into the server
Power controls, console, root password, and snapshots
Open a ticket and follow the conversation