> Godmode v0.19.2 documentation · Reviewed 2026-11-17
> Source: https://godmode.build/docs/v0.19.2/security

# Security and network access

Protect saved keys by keeping Godmode's files private and choosing trusted commands. Software running as your user can read keys; Godmode does not isolate programs or limit provider spending.

## Protect local files

Anyone with both the credential file and its seal key can read your saved keys. Keep both files private.

The default home is `~/.godmode`:

| File | Contents |
| --- | --- |
| `.env.godmode` | Credential names and encrypted values |
| `.env.godmode.<name>` | A separate complete key environment |
| `seal.key` | The key that opens those values |
| `active.json` | Saved environment and business names; no credential values |
| `profile.json` | Business fields as plain JSON |
| `environments/<name>/profile.json` | The environment's own business fields |
| `contexts/<name>/context.json` | Provider key mappings for one business |
| `contexts/<name>/profile.json` | That business's profile |

Encryption reduces accidental disclosure from previews, searches, or a copy of the credential file alone.

Credential and profile files must be regular files owned by you, with mode 0600 in an owned private directory. Godmode rejects unsafe ownership, permissions, and symlinks. It checks for concurrent changes and replaces files atomically. Keep private files ignored and untracked in Git.

## Choose what receives keys

Only trusted programs should receive your keys: they can read, log, or transmit them.

`godmode run` adds selected keys to the child's ordinary inherited environment. Avoid shell tracing and diagnostics that dump the environment.

Pin both selectors for long-running tasks. A saved default affects new unscoped commands in other terminals; it does not redirect an already running Godmode session. Names such as `test` and `live` do not verify the provider account or mode. Check the actual account before changing it.

## Network access

Downloads and member sign-in need internet access. Ordinary key commands work offline without a license check.

| Action | Connection |
| --- | --- |
| Ordinary local commands | No network access or membership check |
| Legacy license commands | Contact godmode.build when explicitly activating or deactivating an older receipt |
| Installer and `godmodeup` | Download releases from godmode.build |
| Opening a provider setup link | Open the provider's website |
| `godmode run` | The child tool controls its own network use |

The membership service receives no provider credentials, profile, or agent instructions. Coding agents and provider tools handle their own data. See [Privacy](/privacy) for site records and infrastructure.

## Inspect a release

Source and build details let you check what runs on your machine.

```sh
godmode source | less
godmode build-info
```

`source` prints the embedded Python engine; `build-info` reports the compiler, dependencies, and engine hash. The [install page](/install) provides matching source and native archives.

To compare an independent build, run these from the reviewed source using the toolchain in `go.mod`:

```sh
sh scripts/build-native.sh
cmp target/godmode-native "$(command -v godmode)"
```

Matching bytes require the same source, compiler, target, and dependencies.

The installer checks SHA-256 checksums. A checksum beside its archive detects corruption, but a compromised publisher could replace both. Release archives are not independently signed or notarized; the license receipt's signature is separate.

## Back up or recover

A lost seal key makes saved credentials unreadable.

Back up every key file you use, including `.env.godmode` and named `.env.godmode.<name>` files, with their matching `seal.key` through a private channel. Also retain `active.json`, your profiles and contexts, and a compatible executable.

If a credential leaks, revoke or rotate it at the provider and update its consumers. Local deletion does not revoke it. Use test credentials in [support requests](/docs/v0.19.2/support).
