Skip to content

Disable env-bound tools when exec server is none#16748

Draft
starr-openai wants to merge 5 commits intomainfrom
starr/ca-410-no-env
Draft

Disable env-bound tools when exec server is none#16748
starr-openai wants to merge 5 commits intomainfrom
starr/ca-410-no-env

Conversation

@starr-openai
Copy link
Copy Markdown
Contributor

Summary

  • make CODEX_EXEC_SERVER_URL=none a first-class disabled environment mode
  • skip project-doc and hierarchical AGENTS injection when the environment is explicitly disabled
  • thread environment capabilities into tool configuration so env-bound tools are omitted when exec/filesystem access is unavailable
  • keep handler-level backstops so bypassed tool registrations still reject safely

Testing

  • just fmt
  • cargo test -p codex-exec-server environment
  • cargo test -p codex-tools disabled_environment_omits_environment_backed_tools
  • cargo test -p codex-tools disabled_environment_capabilities_turn_off_exec_backed_tools
  • cargo test -p codex-core project_doc

starr-openai and others added 5 commits April 3, 2026 18:26
Bazel Windows runners can be slow to launch PowerShell, and these tests
assert auth wiring rather than process-start latency. Match the broader
timeout already used by codex-login provider-auth tests.

Co-authored-by: Codex <noreply@openai.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant