Owen Lin 6075b77001 app-server: ignore persist_extended_history param (#21225) ...

## Why

Taking a step to removing the `persistExtendedHistory` field. It's not
scalable to be persisting so much data in the rollout file and returning
it in the thread history.

When a client explicitly sends `true`, the server now tells that client
the parameter is deprecated and ignored so the caller has a clear
migration signal via the `deprecationNotice` notification.

## What changed

- Keep the `persist_extended_history` / `persistExtendedHistory` field
in the v2 protocol for compatibility, but document it as deprecated and
ignored.
- Ignore the parameter in app-server `thread/start`, `thread/resume`,
and `thread/fork`; those paths always use limited history persistence
now.
- Stop treating `persistExtendedHistory` as a running-thread resume
override mismatch.
- Emit a connection-scoped `deprecationNotice` when a request explicitly
sets `persist_extended_history: true`.

## Verification

- Added `thread_start_deprecates_persist_extended_history_true` to cover
the deprecation notice.
- `cargo test -p codex-app-server`
- `cargo test -p codex-app-server-protocol`

2026-05-05 18:36:13 +00:00

..

schema

Add Windows sandbox readiness RPC (#20708)

2026-05-05 09:58:23 -07:00

src

app-server: ignore persist_extended_history param (#21225)

2026-05-05 18:36:13 +00:00

tests

chore: clean up argument-comment lint and roll out all-target CI on macOS (#16054)

2026-03-27 19:00:44 -07:00

BUILD.bazel

feat: vendor app-server protocol schema fixtures (#10371)

2026-02-01 23:38:43 -08:00

Cargo.toml

Refactor config loading to use filesystem abstraction (#18209)

2026-04-17 00:51:21 +00:00