docs: add GOOSE_PATH_ROOT environment variable documentation (#5678)

Signed-off-by: Rizel Scarlett <rizel@squareup.com>
This commit is contained in:
Rizel Scarlett
2025-11-11 12:06:13 -05:00
committed by GitHub
parent a07023cf77
commit 92d86c0802
2 changed files with 46 additions and 0 deletions
+15
View File
@@ -252,6 +252,21 @@ reuse it. For things like automations or to test without doing official setup, y
set the relevant env vars for that provider. For example `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`,
or `DATABRICKS_HOST`. Refer to the provider details for more info on required keys.
### Isolating Test Environments
When testing changes or running multiple goose configurations, use `GOOSE_PATH_ROOT` to isolate your data:
```bash
# Test with a clean environment
export GOOSE_PATH_ROOT="/tmp/goose-test"
./target/debug/goose session
# Or for a single command
GOOSE_PATH_ROOT="/tmp/goose-dev" cargo run -p goose-cli -- session
```
This creates isolated `config/`, `data/`, and `state/` directories under the specified path, preventing your test sessions from affecting your main goose installation. See the [environment variables guide](./documentation/docs/guides/environment-variables.md#development--testing) for more details.
## Enable traces in goose with [locally hosted Langfuse](https://langfuse.com/docs/deployment/self-host)
- Start a local Langfuse using the docs [here](https://langfuse.com/self-hosting/docker-compose). Create an organization and project and create API credentials.