Define app-server remote history redaction policy

[shiny-code-bot]

Objective

Decide and enforce how much conversation/tool history Every Code should expose through app-server clients before leaning harder on desktop or remote-control surfaces.

Finish Line

Every Code has an explicit app-server policy for which thread history payloads may be returned to remote or desktop clients, with runtime enforcement where app-server exposes history.

Current Status

State: Created from #216 Codex CLI app-server audit.
Next action: Pair this with any implementation of v2 thread resume/read or desktop remote-control compatibility.
Blocked by: None.
Waiting for: Product decision on app-server/desktop remote clients (#217/#37), or implementation work on #226.
Last verified: 2026-05-30.

Scope

• Adapt the concern behind OpenAI Codex commit 7bddb3083d (fix(app-server): thread history redaction for remote clients).
• Define capability- or transport-based redaction for Every Code rather than copying Codex's client-name taxonomy.
• Consider tool output, command output, file content, and payload-heavy events.

Acceptance Criteria

• Remote/desktop app-server clients have a clear history exposure policy.
• Thread resume/read implementations enforce the policy where applicable.
• Tests cover at least one sensitive or payload-heavy history item that should be redacted/omitted.
• ./build-fast.sh passes cleanly after implementation.

Evidence

• Codex CLI added remote-client-specific history redaction after adding richer app-server thread APIs.
• Every Code has v2 thread history protocol types, but runtime app-server support is not yet a first-class desktop/remote API surface.
• This should not block local-only stdio workflows; it matters when data crosses trust boundaries.

Relationships

• Parent audit: Audit Codex CLI app-server parity for Every Code #216.
• Related implementation candidate: Add initial turns page to app-server thread resume #226.
• Remote/desktop direction: Investigate Codex desktop app remote control compatibility #217 and Evaluate upstream app-server remote-control support #37.

Validation

• Run ./build-fast.sh from repo root.
• Add focused tests once an app-server history runtime path exists.