Repository navigation
Per-project environment variables injected into agent runs and dev servers #188
Description
What competitors do
Crystal had a per-project settings file with env (e.g. AWS_PROFILE for Bedrock) (archived README); Conductor documents per-project environment variables (docs); Emdash has .emdash.json.
Solenta today
ProjectInfo is {id, slug, name, path, remoteHost?, remotePath?} (src/shared/ipc.ts:8-18): no env field. Provider spawn config reads only global CODER_*_BIN overrides.
Why it matters
One repo needs AWS_PROFILE=bedrock-prod, another needs a different API base URL or PORT=3001 to avoid dev-server collisions between concurrent threads. Today that is impossible without wrapper scripts on PATH.
Fix direction
Per-project env map in project settings, merged into the spawn environment for runs, dev servers and terminals in that project.
Activity
currentbits commentedon Aug 18, 2026
From the Goose doc-mine: inject AGENT_SESSION_ID and GOOSE_TERMINAL/AGENT marker env vars so shell rc snippets can DETECT agent execution (block git commit interactively, alias hints) and per-session handoff dirs work. Solenta equivalent: SOLENTA_THREAD_ID + SOLENTA=1 in every spawned agent environment.
Per-project environment variables for runs, dev servers and terminals (…
Per-project environment variables for runs, dev servers and terminals (…