Continue anywhere

Continue on your phone while the computer stays on#

1. Open a session in Desktop, or host it with ondago serve.
2. Open its phone link or scan its QR code.
3. Sign in to the same account and register the browser if asked.
4. Open the conversation and send your next message.

The source computer remains the host. Leave it awake and online. A phone link is a destination, not a substitute for account and encryption access.

Continue in the cloud before closing your laptop#

1. Select the session and choose Continue in cloud.
2. Review the project and session being transferred. Resolve any missing repository connection, agent credential, or compatibility decision. If the session uses MCP tools, review where each connection will run.
3. Confirm the transfer using the app’s controls.
4. Follow the transfer progress shown with the session. Wait until Ondago shows that the cloud session is ready or running.
5. Open it on your phone or another computer.

Once the cloud session is ready, the agent can keep working even when this computer is off. Cloud continuation must be available to your workspace and agent. If only a saved snapshot was created, the agent has not begun running in the cloud. A connection configured to Use this computer still needs that computer awake and online, even after the agent starts in the cloud.

With the sandbox release that adds the harness overview, continuing a saved session without a custom first message asks the agent to briefly describe its current setup before resuming: its runtime and model, instruction files, skills, tools, permissions, and any missing context it can verify. The prompt tells it to omit secrets and hidden system instructions. A custom first message takes precedence. Older sandbox releases use the previous continuation prompt.

The current cloud continuation stays associated with its original session. On a phone, the session card follows that continuation, and its continuation history lets you inspect other copies. Open or return the current continuation instead of starting again from a stale local copy.

Continue a saved local conversation#

View planned changes for Continue a saved local conversation. Availability depends on the released app and host versions.

Keep the model selected in a returned Codex session#

View planned changes for Keep the model selected in a returned Codex session. Availability depends on the released app and host versions.

Keep the original agent when continuing a saved session#

View planned changes for Keep the original agent when continuing a saved session. Availability depends on the released app and host versions.

Always On sessions#

Availability: Always On sessions require workspace enablement and are off by default. Ondago turns the feature on for your personal workspace, where the copies are kept, and then each computer chooses whether to use it.

When you turn on Always On sessions in Desktop under Settings, Ondago keeps your most recent Claude Code sessions ready to continue from your phone while the computer sleeps. About 90 seconds after an agent finishes a turn, Ondago saves the session and its project folder, encrypted on your computer, if anything changed. Files your project ignores are not included. While an update is running, the computer stays awake for at most 5 minutes, unless you turned off Prevent sleep. Closing the lid stops updates.

Each session shows one state, such as Always On · ready 14:13, or a pause that names its cause and fix. You can choose Keep Always On or Never keep Always On for a session; the workspace limit (3 per computer by default) decides how many places are used. Other agents show Not available for this agent. A session whose project folder is gone takes no place, and one that already has a copy keeps it without being updated.

When the computer is offline, your phone offers Continue in the cloud from the saved moment and says which moment that is. Always On never starts a cloud run by itself. When you come back, Desktop offers Continue locally. If both versions changed, you choose Bring the cloud work here or Keep working here, and no messages are lost. A copy is deleted when its session no longer qualifies (it is neither kept nor among your most recent sessions, or you chose Never keep Always On), when the session is deleted on the computer, after 7 days with no activity, or when you remove the copies. Choosing Stop keeping only frees the place you reserved: the copy stays while the session is still among your most recent.

Continue in the cloud from a pending plan#

For supported local sessions, plan controls offer Continue in the cloud alongside the local decision actions. In Desktop Overview, selecting a local plan request can show those actions directly in the card; use View plan to inspect the full document first.

The cloud action opens the normal continuation review. It does not approve the local plan first. If you cancel review, the local plan remains waiting for your decision. If you confirm, Ondago uses the session’s ordinary cloud continuation flow. Read-only access, unsupported agents, missing projects, or busy sessions can make this action unavailable; follow the explanation shown.

Bring cloud work back to your computer#

1. Open the cloud session in Desktop and choose Continue locally. Review the destination, then choose Pull.
2. Ondago saves the latest cloud checkpoint and pulls it to this computer. Choose a folder if the original project is no longer available here.
3. For a Git repository, commit or stash local changes before applying returned work when it will land in your checkout (see below). For a plain folder, review any preserved or conflicting file copies reported by the return.
4. Review the returned changes and continue with the installed agent.

From the CLI, inspect runs and collect the result bundle:

ondago runs
ondago list
ondago pull RESULT_BUNDLE_ID -dir ~/projects/example-app -branch -no-open

The branch option keeps the returned result separate from your current commits. Follow the printed instructions to review and resume it.

Understand what the return brought back#

When available, the return report separates the changed files carried by the cloud result from what this pull applied on your computer. A file can already match the result, be updated or deleted by the pull, or keep your local version. If both versions were kept, inspect the reported paths before deciding which to use.

A pull that writes nothing does not necessarily mean the agent did no work: you may already have the same changes. Older results may not include a run-level comparison. Read the per-file outcomes and any capture warnings, then inspect the actual destination folder. For a plain folder without Git, use those file paths rather than branch commands.

Continue with another agent#

1. Choose Continue with another agent for an eligible session.
2. Select an installed destination agent.
3. Read the compatibility report, including instructions, tools, hooks, and permissions.
4. Resolve required choices, then complete the transfer.

Agent-specific features may not transfer exactly. You can preview the same process using ondago migrate SESSION_ID -to AGENT_ID -dry-run.

Ask a teammate to review work#

Use a shared workspace that includes the reviewer. From the CLI, lift a snapshot with -review and optionally -brief-file. The reviewer can open the request, inspect Story, Changes, and Activity, and discuss the work. Resolve the request when it has been addressed.