Configuration for inherited environment variables

[andreagrandi]

What feature would you like to see?

Today I was trying to use a CLI tool which expects an environment variable to be set, otherwise it cannot work.

I have set an env variable named SENTRY_API_TOKEN in my terminal, but running the tool from inside codex was failing.

I asked codex why this was happening and I got this response:

You're right - sorry for the frustration. 
The shell I run in is an isolated sandbox and does not inherit 
your terminal's environment variables, so I can't see your SENTRY_API_TOKEN 
even though your shell has it set. 
Escalation allows network, but doesn't pass env through.

This behaviour doesn't happen with other agents (like Claude Code, Open Code etc...).

In case you have made this choice for "security", you should at least allows the users to decide if codex should inherit the env variables or not, otherwise many tools won't work.

Are you interested in implementing this feature?

No response

Additional information

No response

[futurisold]

Bump!

I wanted to open a similar issue right now. This would be a great feature. I couldn't find any workaround this limitation

[danielchristiancazares]

You can ask it to source the profile you use and it will.

[futurisold]

Actually, I just realized. For my use case, you can simply use the --config to inject the env variable.

E.g.:

codex -c -foo.bar.env.SOME_ENV_VAR="value"

[baron]

Have you tried to set this in ~/.codex/config.toml

[shell_environment_policy]
inherit = "all"

That solved it for me.

[andreagrandi]

Have you tried to set this in ~/.codex/config.toml

[shell_environment_policy] inherit = "all"

That solved it for me.

I just tried this and it doesn't work. I can workaround this specific tool (because I built it) by adding support for config files (so it will read the value from ie ~/.config/sentire/config.json) but I'm concerned for all the other tools where I have no control on them.

[apenney]

I have tried both:

[shell_environment_policy]
inherit = "all"

As well as:

[shell_environment_policy]
inherit = "all"
experimental_use_profile = true

But neither worked - I use https://flox.dev/ for development environments and they rely on the environment being set right. This works totally fine in Claude Code, but I'm unable to get codex to behave at all.

[silouanwright]

This prevents me from using pretty much any CLI tools in Code: Github CLI, Jira CLI, all my custom CLI tools I've made specifically for AI's to use.

[kcosr]

I'm seeing this issue only with specific variables. Does codex filter on "TOKEN" for security? None of the work-arounds from this thread are working for me.

🐳 developer@rocky-dev:/workspace$ env | grep GITLAB
GITLAB_HOST=10.89.1.2
GITLAB_TOKEN=test
🐳 developer@rocky-dev:/workspace$ codex 'run env | grep GITLAB'
...
> Listing environment variables and filtering for GITLAB-related entries.

• Ran env | grep GITLAB

> - GITLAB_HOST=10.89.1.2

[kcosr]

I was able to work around this by creating a function that loads the key from a file and sets it when running the underlying glab command.

glab() { local token; token=$(tr -d ' \n\r' < ~/.gitlab_token); GITLAB_TOKEN="$token" ~/go/bin/glab "$@"; }

[msmans]

This is documented in their config docs — the docs wording is imprecise however:

By default it now passes your full environment to those subprocesses.

But further down, you can see an ignore_default_excludes option that has default of false with comment:

When false, Codex removes any var whose name contains KEY, SECRET, or TOKEN (case-insensitive) before other rules run.

making the previous note that "full environment" is passed in "by default", incorrect.

TL;DR

[shell_environment_policy]
ignore_default_excludes = true

should do it.

[indigoviolet]

nothing in this issue works consistently.

[darinkishore]

having issues on fish!

from fish, i enter zsh, then it finds my shit.
in fish, codex does not find my shit :(
(no path inheritance)

[shell_environment_policy]
inherit = "all"
ignore_default_excludes = true
experimental_use_profile = true

[minorcell]

@andreagrandi

I encountered a similar issue when running Codex in a container environment. I injected some specific environment variables each time I called it, but Codex seemed not to actively read the environment variables to perform the expected actions, such as using the GITHUB_TOKEN to call the API. Initially, I resolved this issue by:

Explicitly stating in the prompt that Codex can read environment variables to do something

However, later I found that Codex seems to be able to explicitly set the environment variable policy in the configuration file config.toml: https://github.com/openai/codex/blob/main/docs/config.md#shell_environment_policy

After configuring it according to this method, the issue was resolved.