Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Evidence record / codex

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-codex-custom-responses-providers-declare-web-and-compaction-capabilities

Custom Responses providers declare web and compaction capabilities. Responses-compatible providers can set model_providers..capabilities.external_web_access and remote_compaction. external_web_access=false prevents live-web hosted search; remote_compaction accepts v2 or unsupported, which uses local compaction. Omitted fields preserve existing provider defaults.

Channel: tagged-release. Half: capability. Date: 2026-10-08 (0.162.0).

Operator consequence: Adapter authors can declare actual backend support without posing as the default provider. Test remote and local compaction and hosted-search behavior before selecting these capabilities on 0.162.0 or later.

Receipt

Finding metadata

Confidence
high

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-codex-custom-responses-providers-declare-web-and-compaction-capabilities

Source links

Primary links, including exact changelog lines when available.

  1. Codex
    commit2026-10-13-codex-custom-responses-providers-declare-web-and-compaction-capabilitiesgithub.com/openai/codex/commit/c6049ebd9694c941386d85fb3e09acab2af289cb

Versioned source: run artifact