Configuration

Files and environment variables

Where Snaga keeps things, what is safe to delete, and the environment variables worth knowing.

Per project

Everything Snaga writes about a project lives in .snaga/ in that project.

Path	What	Safe to delete?
`.snaga/sessions/`	Transcripts and event logs	Yes — loses history
`.snaga/tools/`	Tools the agent wrote: source, `.wasm`, `.policy.toml`	Yes — loses those tools
`.snaga/cache/wasm/`	Precompiled WASM, rebuilt on demand	Yes
`.snaga/memory/snaga.db`	Stored facts	Yes — the agent forgets
`.snaga/eval/runs.sqlite`	Autonomy run registry and baselines	Yes — loses history and baselines
`.snaga/specs-history.jsonl`	Install ledger	Prefer `snaga history prune`
`.snaga/monitors/monitors.json`	Recurring monitors	Yes — monitors stop
`.snaga/trust.toml`	Shell policy and install trust	Yes — reverts to strict defaults
`SNAGA.md`	Project memory, in the project root	Yours — it is a normal file

Deleting the install ledger by hand is the one to avoid: rollback reads it to know what to revert, so removing it strands anything installed. snaga history prune trims it while keeping every entry that touches something still installed.

Per user

Path	What
`~/.snaga/bin/snaga`	The binary
`~/.snaga/credentials.json`	Credentials, when not in the system keychain
`~/.config/snaga/permissions.toml`	Long-term capability policy
`~/.snaga/audit/grants.log`	Append-only capability grant log
`~/.config/snaga/snaga.toml`	Global config

Environment variables

Ordinary use needs none of these.

Behaviour

`SNAGA_NO_NOTIFY=1`	No desktop notification when a long run ends
`SNAGA_NO_PLYAMKA=1`	Plain spinner instead of the mascot
`SNAGA_TOKEN`	API token, instead of stored credentials

Terminal

`SNAGA_NO_STICKY=1`	Disable the pinned input bar
`SNAGA_FORCE_STICKY=1`	Force it on a terminal that was not detected as capable
`NO_COLOR=1`	No colour — the standard variable, honoured

WASM sandbox — each of these removes a guard. Set them when you know why:

`SNAGA_WASM_ALLOW_PRIVATE_NETWORK=1`	Let tools reach private addresses
`SNAGA_WASM_ALLOW_METADATA=1`	Let tools reach cloud metadata endpoints
`SNAGA_WASM_STRICT=1`	Adds a keyword denylist at compile time — the one that tightens
`SNAGA_WASM_EXECUTE_TIMEOUT_SECS`	Per-execution wall-clock limit, default 300

The first two exist because the SSRF guard is occasionally wrong for a legitimate case — a tool that genuinely must reach a service on your own network. They are not general "make it work" switches; see Capabilities and the sandbox.

What to back up

Almost nothing. SNAGA.md if you wrote one, and .snaga/trust.toml if you tuned it — both are small text files worth committing. The rest is either regenerable or history you can afford to lose.