Codex: Lumen ignores environment in Codex
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 297
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
I use codex-cli 0.128.0 (In WSL2) and just installed lumen (In the wsl), but it seems that lumen does not read the environment appropriately like codex does:
Using curl, I can see that ollama is running as expected:
curl http://windix:11434/api/tags
{"models":[
The expected behaviour:
Lumen reads at least its own environment variables like specified in the documentation when running in codex/getting called from codex
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in WSL2 with codex-cli 0.128.0, Lumen, and the shown Ollama endpoint. Start by tracing how Lumen is launched from Codex and how its environment variables are read; done means the documented Lumen environment is available when invoked through Codex, with the behavior verified against the direct curl check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, ollama
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100