DocsOpen app
CLI Ondago documentation

CLI how-to guides

Practical workflows for saving, continuing, moving, and reviewing a session.

Save a session without starting a cloud run#

  1. Open a terminal in the project and find the session ID.
  2. Lift that session with -no-cloud.
  3. List your bundles and keep the new bundle ID to pull it later.
cd ~/projects/example-app
ondago detect -plain
ondago lift -session SESSION_ID -title "Improve checkout" -no-cloud
ondago list

The result is an encrypted snapshot. Later edits to the local session are not automatically part of that snapshot.

Resume on another computer#

  1. Install Ondago and the original agent on the destination computer.
  2. Sign in to the same account, register the device, and select the same workspace.
  3. Choose a destination directory. For a cloud return, commit or stash local edits first.
  4. Find the bundle and resume it.
ondago login
ondago workspaces
ondago config set workspace YOUR_WORKSPACE_SLUG
ondago list
ondago resume BUNDLE_ID -dir ~/projects/example-app

If the device cannot decrypt the bundle, finish workspace-key transfer or recovery in Devices.

Drive a local session from your phone#

ondago serve -cwd ~/projects/example-app -session SESSION_ID -mirror
  1. Open the printed URL or scan the QR code on your phone.
  2. Sign in and complete the phone browser’s device registration.
  3. Read the conversation and send your next message.

The agent still runs on your computer. Keep the serving terminal open and the computer awake. See Continue anywhere if you need the computer to go offline.

Continue a session in the cloud#

For a session that is no longer running locally, lift it without -no-cloud:

ondago lift -cwd ~/projects/example-app -session SESSION_ID -watch

For a supported agent actively working in another terminal, install the hooks, then request a handoff:

ondago init-hooks
ondago handoff -cwd ~/projects/example-app -session SESSION_ID -tool claude-code -note "Finish the tests."

Follow the printed result. A stored bundle does not guarantee that a cloud run started: workspace allowances, agent credentials, repository access, and cloud availability must all permit it. Wait until continuation is confirmed before closing the source computer.

When ready to collect the result, use the result bundle ID:

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

Review the changes on the new branch and use the printed resume command when ready.

For an in-place return, Ondago stops the selected local Claude Code or Codex writer before replacing its transcript. Unrelated sessions stay open. Claude returns replace older copies under the same session ID throughout the configured profile, including copies stored under an earlier project or worktree path. Reopen the existing Claude Desktop Code session after the return. With a custom Claude profile, launch Claude and Ondago with the same CLAUDE_CONFIG_DIR.

If a Claude Code or Codex return is interrupted, choose Retry return. Ondago keeps local recovery files and preserves work found during recovery. If the original session cannot be stopped or the folder is unavailable, choose Continue in another folder to use a separate session copy. The cloud checkpoint stays available. A proven newer local conversation is kept when you pull an older checkpoint. Recovery needs local disk space; its location is shown in the return details.

Continue with another coding agent#

ondago detect -cwd ~/projects/example-app -plain
ondago migrate SESSION_ID -to codex -dir ~/projects/example-app -dry-run

Read what will be preserved, adapted, or dropped. Install the destination agent and resolve required configuration decisions. Then repeat without -dry-run:

ondago migrate SESSION_ID -to codex -dir ~/projects/example-app

The original session remains in its source agent. Use the resume instructions printed for the new session.

Review locally or ask a teammate#

To inspect a session without uploading it:

ondago review open -cwd ~/projects/example-app

To store a session and request a workspace review, write your brief in a file and name the reviewer:

ondago lift -cwd ~/projects/example-app -session SESSION_ID -no-cloud -review reviewer@example.com -brief-file review-brief.md
ondago review list

Use an actual workspace reviewer instead of the example address. Review requests do not grant unrelated accounts access to your encrypted sessions.