What does this PR do?

_get_or_create_env() in code_execution_tool.py builds the container_config dict for the execute_code sandbox, but omitted three docker keys. terminal_tool.py already forwards all three when it builds its own container_config, so execute_code-spawned containers ran without host env vars, forwarded env, or extra docker flags — while terminal-spawned containers had them. The two tools spawn the same kind of container but were not at parity.

This adds the missing keys:

"docker_env": config.get("docker_env", {}),
"docker_forward_env": config.get("docker_forward_env", []),
"docker_extra_args": config.get("docker_extra_args", []),

Concrete symptom: a tool that depends on a host service from inside an execute_code container fails — e.g. a keyring-backed CLI can't reach the host secret service because the docker-default AppArmor profile blocks D-Bus, and the --security-opt apparmor=unconfined override (a docker_extra_args value) never reached the container. The same code under the terminal tool worked.

The keys default to {} / [] / [], so this is a no-op for any setup that doesn't configure them.

Related Issue

No tracking issue — found while debugging a host-service integration that worked under terminal but failed under execute_code.

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)

Changes Made

• tools/code_execution_tool.py — _get_or_create_env() adds docker_env, docker_forward_env, docker_extra_args to container_config
• tests/tools/test_code_execution_container_config.py — 6 tests (forwarding + defaults), mirroring the existing test_file_tools_container_config.py

How to Test

1. Run pytest tests/tools/test_code_execution_container_config.py -q — 6 passed.
2. Set docker_extra_args/docker_env/docker_forward_env in the env config; the container the execute_code tool spawns now receives them (previously only terminal-spawned containers did).

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix
• I've run the affected test suite — tests/tools/test_code_execution_container_config.py: 6 passed
• I've added tests for my changes (6 new tests)
• I've tested on my platform: Ubuntu (Linux 6.8)

Documentation & Housekeeping

• I've updated relevant documentation — N/A
• I've updated cli-config.yaml.example if I added/changed config keys — N/A (keys already exist and are consumed by terminal_tool)
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — N/A
• I've considered cross-platform impact — N/A (Docker-only path, no platform-specific code)
• I've updated tool descriptions/schemas if I changed tool behavior — N/A (no schema change)