Skip to content
OpenComputer

Troubleshooting

Symptoms seen in Slack, each with its cause and fix

Gateway and host logs: Logs and recovery.

No reply

In #eng, Lee mentions @computer and gets a message marked Only visible to you: Computer is not enabled for you yet. Ask the instance owner to add you.
SymptomCauseFix
Only you see: <bot> is not enabled for you yet. Ask the instance owner to add you.You are not in the people list.Ask the installer to add you.
Nothing, in a channelOnly a mention starts a session.Mention @computer.
Nothing, in a session’s thread, without a mentionYou are not in the people list. Only a mention or a new DM gets the notice above.Ask the installer to add you.
Nothing, in a thread shared with other peopleThe session judged the message was for someone else; see Shared threads.Mention @computer in the message.
Only you see: The agent host is offline; your message will be delivered when it reconnects.The host is not connected to the gateway. The message is queued for 24 hours.None if the host reconnects in time; see Logs and recovery.
“is thinking” or :eyes:, then nothingThe host did not answer the gateway within 30 seconds, for example because the runner was still starting. The gateway posts no error.Wait; !status answers once the runner is up.
The turn does not endIt is waiting on an approval or question posted earlier in the thread. These do not time out.Answer it.
“is thinking” or :eyes:, then nothing, self-hostedThe model provider account is out of credits. The self-hosted gateway posts nothing.Check the account’s balance; see Model credentials.

Errors in the thread

computer replies in the thread with a warning sign and: couldn't reach the session: host disconnected
SymptomCauseFix
:warning: couldn't reach the session: <error>The host could not start the runner or hand it the message; <error> is the host’s reason.Send the message again.
:warning: agent process ended: <reason>The harness process exited during the turn.Send a message; the conversation resumes.
:warning: !<command> failed: <reason>A ! command threw an error.
unknown command !x, try !helpThe session has no such command.!help lists them.
can't switch to <model>: <reason>; still on <current>The harness refused the model.See Models and harnesses.
Secrets are not available: the gateway has no SP_STORE_KEY.The gateway has no key to encrypt secrets with.See Secrets and variables.
[attached <name>: could not be downloaded (<reason>)]The runner could not fetch a Slack attachment. A reason mentioning an HTML page: the bot lacks files:read.See Connect Slack.
A file upload fails with missing_scopeThe bot lacks files:write.Add the scope and reinstall the Slack app; see Connect Slack.
preview URLs need an OpenComputer computer; this gateway does not offer themThe self-hosted gateway refuses every preview call.See Preview URLs.
git push or gh fails with gateway not connectedThe host is not connected to the gateway, so it cannot get a GitHub token.Retry when the host has reconnected; see Logs and recovery.
git push or gh fails with GitHub App not set up: <name> missing (run /setup)The GitHub App is not set up.See Connect GitHub.
!diff answers no changes after editsThe session directory is not a git repository; see Branches and pull requests.Ask the session for the diff of a repository.
!status ends with running <commit> · restart to load <commit>The process runs from a source checkout that has moved past the commit it started from.Restart the process.

Stuck turn

SendEffect
!statusThe runner answers during a turn with the session’s status line. No answer: the runner is not reading the thread.
!stop, or the stop buttonStops the turn. The next message continues the conversation.
!restartThe runner restarts when the turn ends (!stop ends it now); the conversation carries over. In one-machine mode it answers “!restart works on a hosted runner; here, restart the process”.

Lost session state

SymptomCause
A dev server or other background process, and its preview URL, is goneThe runner exited after 2 hours without a message; see Idle exit. The conversation and files are kept.
node_modules or another dependency or cache directory is goneGit-ignored build and dependency directories are deleted 24 hours after the session’s last use, while it has no runner. Reinstall or rebuild.
The session directory and its local branches are goneA directory idle for 14 days is deleted if everything was committed and pushed; see Branches and pull requests. The next message gets a new directory from the default branch.
A secret set for “This session only” is goneSession-scope secrets are deleted 30 days after the session was last active.