Codex preview job blocked by fixed briefing capacity with no actionable recovery path
Describe the bug / 描述 bug
An existing Distilly job cannot resume because its briefing exceeds the capacity recorded for the Codex adapter. The error recommends using a larger-capacity host or reducing the research batch, but there appears to be no supported capacity setting for this adapter.
Environment
- Host: Codex CLI 0.146.0
- Distilly: 0.1.0-preview.1
- Platform: Linux ARM64 / Raspberry Pi
- Product line: distilly-plugin
- Node.js version: v22.23.2
- Distilly commit: 5525a4e6adac3e7c1a6c522578513448ae3d7390
Steps to reproduce / 复现步骤
- Resume an existing job with a serialized briefing of 85,819 bytes.
- Request a fresh briefing through distilly_pending, action "brief".
- Observe briefing_too_large.
Actual behavior / 实际行为
The response reports:
- Serialized briefing: 85,819 bytes
- maximumToolResultBytes: 65,536 bytes
- maximumInputTokens: 65,536 tokens
The job remains pending and no patch or commit is created.
Increasing model_context_window to 128000, retaining tool_output_token_limit = 100000, and fully restarting Codex did not change the reported Distilly limits.
Inspection of the installed source found these capacity values in packages/cli/src/host-capacity-fixtures.ts. The production adapter uses that version-specific fixture.
Expected behavior / 期望行为
Please provide a supported recovery path for oversized briefings: a tested larger-capacity binding, capability negotiation, or a documented way to split/reduce the pending batch while preserving its evidence.
The error should explain when changing Codex context settings cannot affect the adapter's recorded capacity.
Is this a known preview limitation, and what is the recommended way to resume an existing affected job?
Source: titanwings/colleague-skill