Runtime unavailable
Get a session running again when its computer, VM, or cloud environment is down.
Every session runs on an execution target: one of your computers, a team VM, or a cloud computer from the team's cloud environment. When that target isn't available, the agent can't run, but the chat history is kept. Fix the target, then continue in the same session.
First, find the target
The session's target shows in the composer and in the session's side panel, for example Cloud machine · Ready or a computer that is Online. Match its state below.
A cloud computer
Cloud computers go to sleep and shut down on their own when idle. Both keep your files.
| You see | What to do |
|---|---|
| Computer asleep | Send a message, or choose Wake up. |
| Computer shut down | Send a message, or choose Start. |
| Unresponsive or Disconnected | Choose Repair session. If that doesn't help, Restart computer (files are kept; running processes end). |
| Workspace unavailable or Failed | Read the error, then choose Repair session. If setup itself failed, fix the environment's setup; see Cloud setup. |
| Computer deleted | The workspace is gone; chat history is kept. Choose Repair session and follow the recovery prompt. Files that were only on the deleted computer cannot be recovered. |
The composer can also show a Cloud environment warning: "This cloud environment is unavailable. Choose another one from the execution target menu." Pick another environment or a computer. If cloud is blocked by your plan or budget, the message says so; see Usage and credits.
Full details: Sandboxes and Runtime recovery.
Your computer or a team VM
| You see | What to do |
|---|---|
| Waiting for (computer) to come online | Open the Alan desktop app on that computer, or start the VM's runtime. Your message runs as soon as it reconnects. |
| Offline | The app or runtime isn't running on that machine. Start it. |
| Reconnecting… | Wait; Alan is restoring the link. |
| Needs attention | Use the action on the machine's row, for example Reconnect, Sign in, or Update Alan. |
| Update required | Run the update command shown, then reconnect. |
| Sign in to (agent) on (computer) | Sign in to the coding agent CLI in a terminal on that machine, then send again. |
Machines are listed in Settings → Account → General → Computers (desktop app) and team VMs in the team's Settings → VMs. See Local execution.
Before switching computers
A cloud computer and your own computer have separate files. Starting a session on another computer does not copy uncommitted work, so recover the original computer when you can. If you do need to switch, commit and push first, then start the new session on the other target.