jif ef8eb8bdd9 [tests] Keep Apps out of generic core test harness (#28508) ...

## Summary

- disable the stable Apps feature in the generic `test_codex()`
integration-test harness
- keep Apps-specific tests explicit: their builders re-enable Apps and
point it at a local mock server

## Why

Generic tests that use dummy ChatGPT auth were also enabling the
host-owned `codex_apps` MCP server. That made unrelated tests contact
`chatgpt.com` and wait for MCP startup, causing the Bazel timeouts
observed on #28368.

The generic harness should be hermetic and should not start an external
service that the test did not request. This is test-only; production
Apps behavior is unchanged. The broader optional-MCP startup behavior is
being handled separately in #28407.

## Testing

- `just test -p codex-core -E
'test(pre_sampling_compact_runs_when_comp_hash_changes) |
test(model_switch_to_smaller_model_updates_token_context_window) |
test(codex_apps_file_params_upload_local_paths_before_mcp_tool_call)'`
- `just fix -p codex-core`
- `just fmt`

ef8eb8bdd9 · 2026-06-16 13:07:43 +02:00

History

..

common

[tests] Keep Apps out of generic core test harness (#28508)

2026-06-16 13:07:43 +02:00

remote_env_windows

Run core integration tests against a Wine-backed Windows executor (#28401)

2026-06-16 00:38:41 +00:00

suite

feat: render typed envelopes for multi-agent v2 messages (#28368)

2026-06-16 11:46:59 +02:00

all.rs

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

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

responses_headers.rs

feat(core): add metadata field to ResponseItem (#28355)

2026-06-15 15:05:28 -07:00