Skip to Content
Referenceoo CLI

oo move-in

Bring this computer's repos, setup, dotfiles and agent tools' setups to your own agent's VM.

oo move-in

Move in: bring this computer's work to your own agent's VM, in one command. oo signs you in if needed, finds your agent (or makes one with --new-agent, showing its price first; at a terminal it asks where to move: one of your agents, a service VM of yours, or a new agent of any runtime or a bare VM), and reads this computer without changing anything: the git repos under the PATHs or --root folders (~/code, ~/src, ~/dev, ~/projects, ~/Developer, ~/work and ~/repos by default) and any other folder or file named as a PATH, a short list of dotfiles, the Node, Python and Homebrew tools you use, and your agent tools' setups: Codex, Claude Code, Gemini CLI, opencode, Hermes, OpenClaw and Cursor's MCP servers.

It then shows everything that would move, and what stays behind, and asks once; nothing runs before that. Your home folder is never a repo. Credentials never move: ~/.ssh, ~/Library, cloud and registry sign-ins and oo's own, wherever they turn up; .env files, keys and certificates, kubeconfigs, Terraform state and variables, .har recordings and secrets files; a shell startup file holding any secret; any untracked file or dotfile that looks like it holds a token, or a user name or password in a URL, and one over 1 MiB that oo can't read for them (--include-unscanned moves those); and in a repo's .git, git-crypt and transcrypt keys, credential settings and remote URLs with a user name or password (its config is written on the VM without them). A repo git-crypt or transcrypt decrypts here stays unless --include-encrypted. A secret-looking file that git tracks, or tracked once, is in the repo's history, which moves with its .git: oo says so. The NAME=value lines of .env files that stay behind are offered as your own secrets on the agent, names only; none is set unless you pick it or name it with --secret. The agent, and anyone who may chat with it, can read what moves into its VM.

Each repo goes to ~/code/NAME on the VM with rsync over one SSH connection through the Sunport (or as oo vm cp sends a folder, where rsync can't), only into a folder oo move-in made and only while it is as oo left it: one the VM had already, or one the agent changed since the last move (a commit, a branch, an edit or a new file), stays as it was, and --to ~/code/NAME-2 moves the repo beside it. So does one whose last copy stopped part way, unless --continue-interrupted. A PATH that is no repo and holds none moves as plain files, but for what its own .gitignore files leave out, to the same place under the VM's home (under ~/laptop/ and its full path from outside home), by the same rules; no .git goes with it. A file named moves as itself, the same way, only where the VM has nothing or over the copy oo left there, unchanged since. --to DIR puts the one PATH named at DIR instead, in the VM's home, by the same rules; --into NAME is the same as --to ~/code/NAME. Dotfiles go only where the VM has none, .gitconfig's identity, aliases and default branch with git config, and shell startup files to ~/.laptop/ for reference. An administrator's move also adds missing packages and runtimes to the Sunport's machine setup (Sunport-wide: new machines get them too; a different version already there stays) and makes the VM a machine. Someone else's agent, or one whose owner oo can't tell without asking, is refused unless --shared, and so is a machine others work on: everyone on it works as one Linux account and can read what moves.

An agent tool's setup moves by a short list of each tool's files (its settings, instructions, commands, prompts, skills and MCP servers), file by file, only where the VM has nothing. Its sign-ins never move (auth.json, .credentials.json, ~/.claude.json but its MCP servers, OAuth files, .env files, OpenClaw's openclaw.json), nor its history, transcripts, sessions, logs or caches. A JSON or TOML config holding a key moves as a copy without it, each key a reference to a variable in the tool's own syntax, and its keys are offered as your secrets; an MCP server with a token in its command, arguments or URL stays, and so does a YAML config with anything secret in it, or any other file with a key written out in it. Nothing is installed, and a folder the agent's own runtime uses is never written: those files go to ~/.laptop/agents/TOOL/, a skill to ~/workspace/skills where its name is free, and SOUL.md never over the agent's own. Sign in on the VM yourself (claude auth login, codex login --device-auth): the agent, and anyone who may chat with it, can use what you sign in to there.

--from-github OWNER/REPO clones a GitHub repo on the VM instead, through OpenOrange's GitHub App, under the same rules; this computer isn't read. Where the VM isn't signed in to GitHub, oo github login runs there in this terminal: you approve on github.com, and the token stays on the VM. A repo the app can't reach stays, with the link that installs the app for it; a rerun fetches. --from-github alone offers the repos the app reaches, none ticked, in the checklist (--yes takes none).

--credentials chooses what of your secrets moves (at a terminal oo asks): none (the default), as above; or all, a full move: .env files, keys, ~/.ssh, ~/.aws and the home folder's other credential places, agent tools' sign-ins and their configs with their keys in them, shell startup files, and repos' git credentials and git-crypt or transcrypt keys, all as they are, each only where the VM has none. oo's own sign-ins, macOS's Library and ~/.ssh/authorized_keys never move, and the secrets found are ticked to set for you on the agent. Everyone who can read the VM can use them.

What --new-agent makes runs what you choose (--runtime): openclaw, hermes, claude-code, codex, gemini-cli, opencode, or none, a bare VM with no agent. By default it mirrors the agent tool you bring with --agents (Hermes or OpenClaw first, then Claude Code, Codex, Gemini CLI, opencode), else OpenClaw; at a terminal oo asks, with that first. Any setup moves into any runtime: one brought into an agent of its own runtime goes where that runtime reads it; OpenClaw's workspace and Hermes' SOUL.md and memories go to the agent's workspace, which every runtime works in; each only where the VM has none, with a copy in ~/.laptop/agents/TOOL/. A new agent takes the SOUL.md, CLAUDE.md, AGENTS.md or GEMINI.md brought as its instructions. Its chat apps you connect yourself (oo agents channels add), once the same bot stops running here.

--vm NAME moves into a service VM of yours instead (oo vm list), and --runtime none makes one: no agent runs there, so every agent tool's setup goes where it reads it, as on this computer. Make an agent of it later, of any runtime: oo move-in --new-agent NAME --agents all in a terminal on that VM (oo vm shell NAME).

--plan prints the plan and changes nothing, for a new agent when you have none yet; --json prints it, and what was done, as JSON. A rerun goes on from where one stopped, and copies again only what changed.

oo move-in [options] [PATH ...]
ArgumentRequiredDefaultChoicesDescription
PATHnoa repo, a folder to find repos in, or any other folder or file, moved as plain files; default the --root folders
--agent AGENT_IDnoyour agent to move into, by its ID from oo agents list
--new-agent NAMEnomake a new agent of your own with this name, its price shown first, and move into it
--vm NAMEnoa service VM of yours to move into, by its name from oo vm list, where no agent runs
--runtime RUNTIMEnoopenclaw, hermes, claude-code, codex, gemini-cli, opencode, nonewhat runs what --new-agent makes: openclaw, hermes, claude-code, codex, gemini-cli, opencode, or none (a bare VM, no agent); by default what the agent tool you bring ran, else openclaw; at a terminal oo asks, with that first
--credentials CREDENTIALSnonone, allnone: secrets stay here (the default; at a terminal oo asks); all: a full move, every secret and credential too, as it is
--root DIRnoa folder to find repos in, four levels deep; repeat for more; replaces the defaults
--from-github OWNER/REPOnoclone this GitHub repo on the VM instead of reading this computer; repeat; alone, pick from the repos the app reaches there
--exclude GLOBnoleave out paths in repos, or whole repos, matching GLOB, such as '*.mp4' or build; repeat
--skip STEPSnoleave out steps, comma-separated: setup, machine, repos, dotfiles, agents, secrets
--agents TOOLSnobring these agent tools' setups, comma-separated: codex, claude, gemini, opencode, hermes, openclaw, cursor, or all; without it none move (at a terminal oo asks which), and the plan lists the ones here
--secret NAMEnoset this secret for you on the agent, from a .env file or an agent tool's config that stays behind; repeat
--resume-secrets MOVEnoreuse the secret selection saved by the unfinished move named in its rerun command
--plannoprint the plan and change nothing
--jsonnoprint the plan and the outcome as JSON
--yesnostart without the checklist, as the plan shows it
--sharednomove into someone else's agent, or a machine others work on as well, who can read what moves
--to DIRnowhere on the VM the one PATH goes, in its home (~/work/api, or an absolute path in it), such as when one of its name is there already
--into NAMEnothe same as --to ~/code/NAME
--continue-interruptednocopy into a repo's folder on the VM whose last copy stopped part way, over whatever the agent changed there since
--include-unscannednoalso move untracked files and dotfiles over 1 MiB, which oo doesn't read for tokens, and agent tools' binary files (not images or fonts), which it can't read for keys
--include-encryptednoalso move repos git-crypt or transcrypt decrypts here: their files move readable; their key never does

It also takes the connection options.

On this page