1.10.0: your .env is read now
As of 2026-07-25. A snapshot; follow the links for what changed since.
npx mulmoterminal@latest reads the .env where you ran it
Who needs to act: anyone using a provider (OpenRouter and friends) with the API key in a .env.
The help said a key belongs “in the shell that starts MulmoTerminal, or a .env beside it”. That was true of a dev launch and false of every real one — only yarn server passed the flag, so a key written into .env never reached the server and the provider stayed unusable with nothing to explain why.
How to use it
Put .env in the directory you type the command in.
cd ~/projects/myapp
echo 'OPENROUTER_API_KEY=sk-or-...' >> .env
npx mulmoterminal@latest
It reads from your shell’s directory, not the workspace — the same place unless --cwd says otherwise.
Two things worth knowing
Both were measured rather than assumed, and both are pinned as tests:
- A name already set in your shell is not overridden by
.env. .envvalues reach theclaude/codexsessions too, since a session inherits the server’s environment.
→ Using another model via OpenRouter
Windows: one path rule instead of eight
Path containment was hand-rolled in eight places and broke wherever the two sides came from different sources — a differently-cased directory silently refused file serving or skipped preset seeding. One rule now, and the Windows CI job is green for the first time.