Configuration
Everything under ~/.sandwalk/, environment variables, and LAN server authentication.
On-Disk Layout (~/.sandwalk/)
Everything Sandwalk stores lives in open formats under ~/.sandwalk/:
| Path | Contents |
|---|---|
config.json | Providers, API keys, default model, sandbox & memory preferences |
mcp.json | MCP servers (mcpServers), Cursor-compatible (including omnigraph stdio MCP) |
skills/ | Installed & crystallized skills (<slug>/SKILL.md + references/) |
memory/ | USER.md, MEMORY.md, memory.db, wiki/<scope>/*.md, and omni/<scope>/graph.omni |
bin/ | Managed local binaries (omnigraph, omnigraph-server, sandwalk-omnigraph-mcp) |
workspaces/<session>/ | Per-session artifacts: uploads/, outputs/, plans/, project/ |
data/ | Local scientific datasets from sandwalk data pull (DepMap, MSigDB, STRING) |
agent-server.db | Sessions, Specialists, and messages shared by the CLI and Desktop/Web UI |
Inspect or update configuration from the CLI:
sandwalk config show
sandwalk config set <key> <value>Environment Variables
Provider keys can also be supplied via standard environment variables (OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, OPENROUTER_API_KEY, XAI_API_KEY, DEEPSEEK_API_KEY, MOONSHOT_API_KEY). Modal cloud sandboxes use MODAL_TOKEN_ID and MODAL_TOKEN_SECRET (or modal setup).
Protecting a LAN / Remote Server (sandwalk auth)
When exposing sandwalk serve --host 0.0.0.0 across your LAN, Mac mini, or HPC node, enable API key authentication:
sandwalk auth generate
sandwalk auth enable
sandwalk serve --host 0.0.0.0Last updated on