Prepare the destination#
Follow Install on the remote host. Run these checks in your agent's shell or runtime.
command -v godmode
godmode --version
godmode activeFor the default installation, source ~/.godmode/env or use ~/.godmode/bin/godmode. For a custom home, set GODMODE_HOME or pass --home when calling the binary.
Supply the required keys#
Use the provider's login flow or add keys on the remote host with godmode setup PROVIDER. See Credentials for imports and command examples.
Copy a complete key file#
A key file and its matching seal.key give the destination access to every key in that file. Use a fresh remote home. Existing named environments may rely on the seal key already on the destination.
Replace devbox with your SSH host.
ssh devbox '
umask 077
remote_godmode="$HOME/.godmode-remote"
mkdir "$remote_godmode" &&
curl -fsSL https://godmode.build/install.sh -o "$remote_godmode/install.sh" &&
sh "$remote_godmode/install.sh" --home "$remote_godmode" --install-only
'Continue after this succeeds. If the directory exists, choose a new destination. On the source host, confirm the path with godmode --env default --context - path. Migrate older plain-text keys first. This example copies from the standard home.
scp -p ~/.godmode/.env.godmode ~/.godmode/seal.key devbox:.godmode-remote/ &&
ssh devbox '~/.godmode-remote/bin/godmode --home ~/.godmode-remote --env default --context - list'scp -p preserves mode 0600. The list confirms which names are saved. For a named environment, use the key path from godmode env show NAME, copy that file with its matching seal key and replace --env default with --env NAME.
To bring the default business details too, copy profile.json separately with scp -p. A profile-only transfer needs just that file. See Businesses and environments for named profiles.
Connect the agent#
Run godmode agents in the remote shell with the chosen home. Review the destination before saving the note, then start a fresh agent session. Use scoped agent instructions or pin both selectors in a scheduled task.
Use a read-only provider request to check the remote tool's account. Copies are snapshots. Save rotations on each machine and revoke keys at the provider when a host should lose access.