Back to Signal Feed
CodeTracked since May 22, 2026

Strip unsupported suppressOutput from Codex hook output

In PR #2499, the Codex adapter now removes `suppressOutput` from the serialized hook result so Codex CLI no longer receives a Claude-only field. This fixes the regression where every affected hook call could fail with `PostToolUse hook returned unsupported suppressOutput` when hooks shared a common `HookResult` object.

Codex CLIsuppressOutputbuildBaseOutput()src/cli/adapters/codex.ts

What Happened

  • In PR #2499, the Codex adapter now removes `suppressOutput` from the serialized hook result so Codex CLI no longer receives a Claude-only field. This fixes the regression where every affected hook call could fail with `PostToolUse hook returned unsupported suppressOutput` when hooks shared a common `HookResult` object.
  • In PR #2499, the Codex adapter now removes `suppressOutput` from the serialized hook result so Codex CLI no longer receives a Claude-only field. This fixes the regression where every affected hook call could fail with `PostToolUse hook returned unsupported suppressOutput` when hooks shared a common `HookResult` object.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Changed the Codex output serialization path to strip `suppressOutput` before printing hook output, while keeping the Claude Code adapter behavior intact, and added/updated hook-output tests to lock in the corrected payload shape.

Why Track This

Why It Matters

Developers and operators using Codex through claude-mem will see tool/hook calls stop failing on unsupported output fields, so automated flows can continue without unexpected CLI aborts. The patch enforces a clean output contract in `src/cli/adapters/codex.ts` by filtering the Claude-only `suppressOutput` flag before stdout emission; the key follow-up is to continue monitoring other adapter changes for similar leakage of unsupported hook fields that could reintroduce CLI hard failures.

Impact

Developers and operators using Codex through claude-mem will see tool/hook calls stop failing on unsupported output fields, so automated flows can continue without unexpected CLI aborts. The patch enforces a clean output contract in `src/cli/adapters/codex.ts` by filtering the Claude-only `suppressOutput` flag before stdout emission; the key follow-up is to continue monitoring other adapter changes for similar leakage of unsupported hook fields that could reintroduce CLI hard failures.

What To Watch Next

  • Watch whether Codex CLI becomes a repeated pattern.
  • Track follow-up changes around AI Coding Agents.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: unsupported_cli_field_leakage, adapter_output_schema_drift.
Open Topic TimelineOpen Technical EventOpen Original Sourceunsupported_cli_field_leakage / adapter_output_schema_drift / regression_after_hook_result_refactors

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

thedotmack/claude-mem PR #2499: fix(adapters/codex): strip suppressOutput from Codex hook output (2486)

A focused patch in `src/cli/adapters/codex.ts` unconditionally removes `result.suppressOutput` inside `buildBaseOutput()`, and regression tests were updated to assert the emitted output lacks that field.