Skip to content

Remote machines

Set up Godmode on the machine where your agent runs. Keys and profile stay on the host where you save them; copies do not synchronize.

You are reading the v0.19.2 documentation. Open the current docs.

More formats
Raw Markdown ↗

Prepare the destination#

Your remote agent cannot use an installation that exists only on your laptop.

Follow Install on the remote host. Then use Quickstart to connect the account and agent. Check what the remote shell uses:

command -v godmode
godmode --version
godmode active
godmode path

For a default install, a non-interactive shell can source ~/.godmode/env or run ~/.godmode/bin/godmode directly.

For a custom home, select it explicitly. Installing the binary there does not select its data directory:

export GODMODE_HOME=/srv/private/godmode
"$GODMODE_HOME/bin/godmode" path

Replace the example path with an owned private directory. Keep PATH and GODMODE_HOME consistent in the SSH shell, scheduler, and agent runtime.

The saved active pair belongs to that Godmode home; it does not synchronize from your laptop. Create the required environment and business on the destination, then select them. Pin --env and --context in scheduled tasks or scoped agent notes so another local default change cannot redirect their next command.

Supply the required keys#

Give this host only the accounts its tasks need.

Use the provider tool's native login or save the keys this host needs with godmode setup SLUG or godmode set NAME. See Credentials.

Copying .env.godmode and seal.key gives the destination every key in that store. To transfer a whole store to a trusted host:

  1. Inspect and privately back up its existing store before replacing anything.
  2. Stop concurrent changes and transfer the matching pair through an authenticated private channel. Keep ownership and mode 0600.
  3. Verify godmode path and godmode list on the destination.

Never replace only half of a sealed store. Migrate a legacy plaintext store first. Keep credentials out of Git, images, and prompts. Copy only profile.json when you need business details without keys; it also contains private data.

Connect the agent#

The remote agent needs Godmode’s note in its own instruction files.

Run godmode agents and review the destination's instruction paths. Start a fresh agent session, run godmode help, and make a read-only check of the intended provider account. When a key rotates, update each required host and deployment separately.

Revoke or rotate provider keys when it should lose access; deleting local files does not revoke them.

Godmode v0.19.2 · 2026-11-17 · Inspect the source · Get help