Install Genesis declaratively with nix-genesis — a batteries-included Home Manager module.
What you get
- Gateway + macOS app + tools (whisper, spotify, cameras) -- all pinned
- Launchd service that survives reboots
- Plugin system with declarative config
- Instant rollback:
home-manager switch --rollback
Quick start
Install Determinate Nix
If Nix is not already installed, follow the [Determinate Nix installer](https://github.com/DeterminateSystems/nix-installer) instructions.
Create a local flake
Use the agent-first template from the nix-genesis repo:
```bash
mkdir -p ~/code/genesis-local
# Copy templates/agent-first/flake.nix from the nix-genesis repo
```
Configure secrets
Set up your messaging bot token and model provider API key. Plain files at `~/.secrets/` work fine.
Fill in template placeholders and switch
```bash
home-manager switch
```
Verify
Confirm the launchd service is running and your bot responds to messages.
See the nix-genesis README for full module options and examples.
Nix-mode runtime behavior
When GENESIS_NIX_MODE=1 is set (automatic with nix-genesis), Genesis enters a deterministic mode that disables auto-install flows.
You can also set it manually:
export GENESIS_NIX_MODE=1
On macOS, the GUI app does not automatically inherit shell environment variables. Enable Nix mode via defaults instead:
defaults write ai.genesis.mac genesis.nixMode -bool true
What changes in Nix mode
- Auto-install and self-mutation flows are disabled
- Missing dependencies surface Nix-specific remediation messages
- UI surfaces a read-only Nix mode banner
Config and state paths
Genesis reads JSON5 config from GENESIS_CONFIG_PATH and stores mutable data in GENESIS_STATE_DIR. When running under Nix, set these explicitly to Nix-managed locations so runtime state and config stay out of the immutable store.
| Variable | Default |
|---|---|
GENESIS_HOME |
HOME / USERPROFILE / os.homedir() |
GENESIS_STATE_DIR |
~/.genesis |
GENESIS_CONFIG_PATH |
$GENESIS_STATE_DIR/genesis.json |
Service PATH discovery
The launchd/systemd gateway service auto-discovers Nix-profile binaries so
plugins and tools that shell out to nix-installed executables work without
manual PATH setup:
- When
NIX_PROFILESis set, every entry is added to the service PATH in right-to-left precedence (matches Nix shell precedence — rightmost wins). - When
NIX_PROFILESis unset,~/.nix-profile/binis added as a fallback.
This applies to both macOS launchd and Linux systemd service environments.
Related
- nix-genesis -- full setup guide
- Wizard -- non-Nix CLI setup
- Docker -- containerized setup