Ondago Cloud may appear as Secure Cloud in your installed app.
Stop a Codex turn or a background command#
View planned changes for Stop a Codex turn or a background command. Availability depends on the released app and host versions.
Codex says this conversation is open in another app#
Codex lets one program write to a conversation at a time. If you run codex resume while Ondago has that session open, Codex shows This conversation is open in another app. The other app is Ondago. This can also appear just after you bring a session back from the cloud, because Ondago opens it on this computer to tell the agent it has returned.
The terminal cannot find ondago#
On macOS or Linux, check whether ~/.local/bin is on PATH. Follow the installer’s instructions, then reopen your terminal. On Windows, open a new PowerShell window after installation.
ondago versionIf the installed version is unexpected, use command -v ondago on macOS/Linux or Get-Command ondago in PowerShell to see which binary runs.
My session is missing#
- Confirm the agent has actually created a session in the intended project.
- Check the workspace, location, search text, and active filters.
- Refresh or rescan from Desktop and let discovery finish.
- Check the project directly with the CLI.
ondago detect -cwd ~/projects/example-app -plain
ondago machine sessions -jsonUse the actual project path. A supported capture format does not imply every agent also supports live control.
Web activity appears as JSON in a transcript#
View planned changes for Web activity appears as JSON in a transcript. Availability depends on the released app and host versions.
Antigravity appears twice and one conversation is empty#
View planned changes for Antigravity appears twice and one conversation is empty. Availability depends on the released app and host versions.
Blank space below a local conversation#
View planned changes for Blank space below a local conversation. Availability depends on the released app and host versions.
Claude sessions named auth or Warmup#
Claude Code can write internal subagent initialization exchanges with the prompt Warmup. These are not messages you typed. An older Claude Code executable can also interpret an unsupported auth status check as a conversation prompt.
Check claude --version on the affected computer. Account checks require Claude Code 2.1.41 or newer. If multiple installations exist, use command -v claude on macOS/Linux or Get-Command claude in PowerShell to identify the executable.
Sessions have the same title#
Matching titles do not necessarily mean the conversation was duplicated. Older Desktop and CLI versions can name Codex conversations after their injected AGENTS.md instructions. A Ondago Cloud recovery backup can also share its running session’s title.
The same update keeps cloud subagents nested under their parent session when local subagents are also present.
Desktop cannot verify the CLI connection#
Run ondago version in a terminal. If the CLI is killed or stops before printing its version, reinstall it using the CLI installer, then choose Check again or Retry setup in Desktop. A working sign-in does not repair an executable that cannot start.
My computer is offline or cannot accept messages#
Every computer shows Online or Offline since the time it last checked in (for example Offline since 02:14) wherever it appears: under its name in the Overview, in the place filter on narrower windows and tablets (whose button adds a count such as All places · 1 offline), beside each of its sessions on your phone (for example Work Mac · Offline since 02:14), when you choose where a new session runs, and in Computers. A computer reads as offline about 90 seconds after it stops checking in. Ondago cannot tell whether it went to sleep, lost its connection or quit, so it says offline rather than guessing.
Starting a session on an offline computer is refused before anything is sent, with a sentence such as Work Mac is offline since 02:14. Choose another place, or start it there once the computer is back online. If the computer goes offline while a start is waiting for it, Ondago withdraws that start and keeps your message. If the computer had already received the session, it may start when the computer is back, so check Sessions before starting it again.
In a session that is open on an offline computer, the message box is replaced by a notice that the computer is offline. You can still read the conversation. A message that had not been sent yet goes back into your draft, marked Not sent, so nothing is delivered late. When the computer is back, the session reconnects and the message box returns with your draft. During the first 90 seconds or so of a drop, before the computer reads as offline, the session says it is reconnecting and a message you send waits as Sends when reconnected.
ondago machine status -json
ondago machine ensureCheck that the computer is awake and connected. If you want remote access, enable it:
ondago machine enableIf the computer is online but lists no sessions, check which agent histories it may read with ondago machine history. With none allowed, it reports none.
If a conversation has not synced, open an updated Desktop app on the source computer and let it sync while online. Reading copies expire 72 hours after source activity. Check the last-sync time, your account, and personal-vault key access; refreshing a copy does not extend its retention.
I can sign in but cannot open a saved session#
Check that the workspace is correct, the device is registered, and the workspace key has reached this device. Use Devices or your recovery flow. Clearing browser data or changing ONDAGO_CONFIG_DIR can make a previously working device lose access to its local keys.
See Devices, access & recovery. Signing in again alone does not replace a missing decryption key.
A cloud continuation did not start#
View planned changes for A cloud continuation did not start. Availability depends on the released app and host versions.
A cloud run stopped with an error#
View planned changes for A cloud run stopped with an error. Availability depends on the released app and host versions.
Claude Code has not trusted this folder yet#
View planned changes for Claude Code has not trusted this folder yet. Availability depends on the released app and host versions.
An MCP tool is missing in a cloud session#
Open MCP connections and read the latest setup result. A running agent does not guarantee that every tool connection initialized. Retry a supported connection or update its credentials when offered; approval and configuration changes require source review and a new continuation.
For Use this computer, confirm that the original computer is awake and online. An account-only vendor connector may not have local configuration to discover. Follow the connection repair guide.
A slash command is missing or cannot run#
The command menu depends on the active agent, connection, and discovered commands or skills. It does not reproduce every command from the agent’s terminal UI. Reconnect or update the source installation if the host does not offer commands, and follow any wait-for-idle or unsupported-action explanation. See supported command behavior.
Project instructions were not written to disk#
A saved draft is not yet published knowledge. Open Write agent files, complete the publish step if needed, and select an online computer with the project folder. Check each file’s result: blocked adaptations or edits inside an existing managed block can prevent that write. Keep your edits and resolve the reported difference before retrying. Follow the agent-files guide.
A returned session refuses to apply#
If a Git return refuses changes in the working tree, commit or stash your edits, confirm that the destination is the right repository, then retry. Use -branch -no-open to collect the result on a separate branch and inspect it before continuing. For a plain folder, review the per-file outcomes and any copies kept alongside your files. Understand the return report before replacing a local version.
- The first line names the step that failed, such as a checkout. A bare
exit status 1is any subprocess, so the lines after it are the evidence. - A line saying untracked files would be overwritten by checkout means files in your folder are in the way. Move or commit them, or pull into another folder. Cloud work for a GitHub-started session lands beside a checkout that is not on the commit the run started from, so this should be rare.
- Output from a hook, for example from
post-checkout(husky, lefthook or Git LFS), means a hook in the destination failed. Ondago does not run your hooks when it creates its own folder beside a checkout. A pull that checks a commit out in your own checkout (a session from another computer) still runs them. - A sentence saying the pull stopped before changing anything (uncommitted changes, newer commits, or a session already on this computer) means nothing was written. When the CLI did not say that, the sheet adds that files may have changed: check the destination before starting over.
After a pull that failed before importing anything, Continue in another folder is the main action, for every agent, and Review options returns to the same form. A pull stopped for uncommitted changes or newer commits offers Change options, Pull into another folder and Try again, with Try again as the main action. If the conversation was already imported, or Ondago kept a recovery record, the retry stays the main action. Read how a cloud session is pulled beside your checkout for the cases where the work lands in a separate folder; the sheet then says your folder was not changed and gives the reason: how many commits behind it is, or how many commits of its own the run never saw.
The connection ended#
Your loaded messages and draft remain in the view. Tap the small Refresh connection icon beside Connection ended above the composer to check again. Refresh checks the connection without resending messages. If the session is no longer available, it stays ended. Use Connection details for more information.
A message is queued, unavailable, or uncertain#
View planned changes for A message is queued, unavailable, or uncertain. Availability depends on the released app and host versions.
Readable search results#
View planned changes for Readable search results. Availability depends on the released app and host versions.
Compacting instead of Working#
View planned changes for Compacting instead of Working. Availability depends on the released app and host versions.
Opening a live session#
View planned changes for Opening a live session. Availability depends on the released app and host versions.
A session or screenshot does not reopen#
A session already running on your computer should reconnect to its existing live host. Keep that computer awake and online, then reopen the session. Do not start another copy of the agent to regain control.
Attached screenshots appear as thumbnails; select one to open the viewer, download it or retry loading. Keep the host connected while loading an uncached image.
View planned changes for Onboarding improvements in the next update. Availability depends on the released app and host versions.
Get help#
Use the app’s contact page or email team@ondago.ai. Include your operating system, CLI version, app version if available, the action you took, and the visible error. Use demonstration content or mask private data in screenshots. Omit credentials and recovery material.