jif 1391d786bc Scope command approvals by execution environment (#28738) ...

## Why

Command approval cache keys included the command and working directory,
but not the execution environment. An approval for `/workspace` locally
could therefore be reused for the same command and path on an executor.

## What changed

- Include the selected environment ID in shell and unified-exec approval
cache keys.
- Carry that ID through the normal command approval request so clients
can show which environment is being approved.
- Expose the environment through app-server as a required nullable
`environmentId` and show it in the inline TUI approval prompt.
- Keep older recorded approval events compatible when the environment is
absent.

For example, `echo ok` in local `/workspace` and `echo ok` in executor
`/workspace` now produce different approval keys and separate prompts.

## Scope

This PR does not change network approvals, Guardian review actions, MCP
elicitation, full-screen TUI rendering, or environment-ID validation.
Remote `shell_command` execution itself remains in #28722; this PR only
makes its approval key environment-aware.

1391d786bc · 2026-06-17 19:52:43 +02:00

History

..

src

Scope command approvals by execution environment (#28738)

2026-06-17 19:52:43 +02:00

tests

[codex] Use expect in integration tests (#28441)

2026-06-15 21:53:47 -07:00

BUILD.bazel

[bazel] Bump rules_rs and llvm (#13366)

2026-03-04 01:59:32 +00:00

Cargo.toml

[codex] Load user instructions through an injected provider (#27101)

2026-06-11 19:28:47 +00:00