Add explicit OpenAI conversation compaction and fix Anthropic compaction - #61370
Merged
Conversation
nathansobo
force-pushed
the
manual-openai-compaction
branch
from
July 22, 2026 14:07
1917db6 to
bbd0f4f
Compare
- Document supersede semantics of provider-native compaction replay - Add context to malformed compaction payload errors and assert on it instead of serde_json's internal error text - Use the model's provider in the Cloud compaction request body instead of hardcoding OpenAI
Several backends share the OpenAI Responses request conversion and event mapper (OpenAI itself, Zed Cloud's OpenAI models, OpenAI-compatible endpoints, Codex, OpenCode, and Bedrock Mantle), but their encrypted compaction items are not interchangeable: only the backend whose infrastructure produced an item can decrypt it. Previously the shared converter accepted any state stamped with the OpenAI provider id and the shared mapper stamped every backend's compaction output with that id, so compacting with OpenAI and then switching to another Responses-protocol backend would discard the entire transcript in exchange for an opaque blob that backend cannot read. Thread the owning backend's provider id through into_open_ai_response, OpenAiResponseEventMapper, and the compaction state helpers so replay is limited to state the target backend produced; foreign state falls back to replaying the full transcript. Also surface malformed streams that end mid-compaction: Anthropic's mapper now errors when the message stops with an unclosed compaction block, and the OpenAI mapper errors when a response completes with a compaction item that was added but never finished, instead of leaving consumers with a Started event and no terminal signal.
…actions Anthropic's compaction protocol attaches opaque encrypted_content to compaction blocks and requires it to be round-tripped verbatim. Deltas carry it as a whole-value replacement (like thinking signatures), so the mapper keeps the latest value rather than concatenating chunks. The finalized summary now carries it as owner-scoped provider state, and replay only includes it when the request targets the backend that produced it, mirroring how OpenAI Responses compaction state is scoped. A compaction block that closes without content is Anthropic's documented representation of a failed compaction (the server treats it as a no-op), so surface it as CompactionUpdate::Failed instead of erroring out the rest of the response.
Compaction requests consume tokens like any other completion, but the usage OpenAI reports on /responses/compact was parsed and then dropped. LanguageModel::compact now returns a CompactionResult pairing the compacted context with that usage so callers can display what the compaction cost.
The Responses API documents the top-level instructions field as a system message inserted into the model's context on each request. Sending the system prompt there instead of as system-role input items fixes a hole in compaction replay: replaying provider compaction state replaces all accumulated input items with the canonical window, which previously discarded the current system prompt and left the model running on whatever prompt was frozen into the window at compaction time. This also unifies the Responses backends: the Codex backend rejects system-role input items and always required the instructions form, so its post-hoc extraction is no longer needed (it still always sends the field, as it always has). Compact requests inherit the field, so explicit compaction now runs with the current system prompt in context as well. NOTE: Zed Cloud's typed completion request currently has no instructions field and will silently drop it; cloud must deploy that field before this change ships to users.
nathansobo
enabled auto-merge
July 24, 2026 16:53
as-cii
self-requested a review
July 24, 2026 17:04
Member
|
@zed-industries/approved |
mdz-axo
added a commit
to mdz-axo/zed-kask
that referenced
this pull request
Jul 25, 2026
Upstream changes (zed-industries/zed main, 27 commits): - agent: Add agent.compaction_model setting for context compaction (zed-industries#60012) - agent: Show effort selector for anthropic compatible providers (zed-industries#61579) - acp: Update agent-client-protocol SDK to 2.0.0 (zed-industries#61570) - client: Extract proxy handshakes into new proxy_handshake crate (zed-industries#61427) - collab: Fix multiworkspace location out of sync bugs (zed-industries#61598) - editor: Fix sticky header drag cancels autoscroll (zed-industries#53592) - editor: Fix crash when copying and pasting using multiple cursors (zed-industries#61545) - editor: Skip untitled buffers when saving a multi-buffer (zed-industries#61380) - gpui: Fix images not being drawn with rounded corners with ObjectFit::Cover (zed-industries#61383) - gpui: Fix deadlock in performance profiler and reenable it (zed-industries#61584) - git_ui: Prevent Git panel bindings in repository selector (zed-industries#61282) - language_model: Add explicit OpenAI conversation compaction and fix Anthropic compaction (zed-industries#61370) - markdown: Fix squashed Mermaid diagrams in markdown preview (zed-industries#61260) - Opus 5 BYOK Support (zed-industries#61596) - repl: Show add-cell controls in empty notebooks (zed-industries#61329) - search: Escape seeded buffer search query in regex mode (zed-industries#57748) - settings: Fix VS Code import appending duplicate file associations (zed-industries#61355) - settings: Split VSCode and Zed keymap files (zed-industries#61532) - Treat blank spawn_agent session IDs as absent (zed-industries#60893) - worktree: Reload git state when a watcher rescan covers a repository (zed-industries#61541) - Plus 7 more minor fixes. Merge fixes: - crates/agent/src/thread.rs: replay_tool_call used 'message_ix' (undefined) after auto-merge; renamed to 'owning_message_ix' (the parameter name). - Cargo.toml: Removed stale workspace members hkask-wallet and hkask-git-cas (both directories deleted in prior commits but workspace entries remained). - kask/crates/hkask-regulation/src/wallet_manager.rs: Stubbed consume() and settle_rjoules() on WalletBudgetPort — these were API-key encumbrance operations from the deleted hkask-wallet crate; regulation tracks per-agent gas balances, not per-key encumbrances. - kask/crates/hkask-regulation/src/wallet_gas_calibrator.rs: Fixed test to use crate::agent_wallet_store::WalletStore instead of hkask_storage::WalletStore. - kask/crates/hkask-regulation/Cargo.toml: Added tokio macros feature to dev-dependencies for #[tokio::test]. - kask/crates/kask_bridge/Cargo.toml: Added futures dependency (needed by context_injector.rs for futures::executor::block_on). - kask/crates/kask_bridge/src/context_injector.rs: Fixed futures_util::executor to futures::executor (futures-util doesn't include executor module). Release Notes: - N/A
0arm
pushed a commit
to 0arm/zed
that referenced
this pull request
Jul 26, 2026
…ion (zed-industries#61370) # Objective Add explicit conversation compaction for OpenAI Responses API models, available through both direct OpenAI connections and Zed Cloud models. Keep finalized replacement context provider-neutral and separate from the lifecycle events emitted while automatic compaction is in progress. ## Solution - Add opt-in explicit compaction support to the `LanguageModel` trait. - Separate streamed `CompactionUpdate` lifecycle events from finalized `CompactedContext`. - Represent provider-native compacted context as an opaque, versioned state owned by the originating provider. - Construct compact requests through the same OpenAI request conversion used for completions, then narrow the request to fields supported by `/responses/compact`. - Preserve and validate the complete canonical replacement window returned by OpenAI. - Replay the replacement window before messages sent after compaction, without resending the superseded transcript. - Support explicit compaction through both the direct OpenAI provider and `CloudLanguageModel`. - Update automatic OpenAI and Anthropic compaction to use the same finalized context representation. - Reject empty, malformed, incorrectly versioned, and incorrectly owned provider state. The corresponding Cloud change adds the `/completions/compact` proxy route: https://github.com/zed-industries/cloud/pull/3099. The downstream Delta UI integration is https://github.com/zed-industries/delta/pull/1739. ## Testing - `cargo nextest run -p anthropic -p open_ai -p language_models_cloud` - `cargo check -p language_models --tests` - `cargo fmt --all --check` - `git diff --check` The focused tests cover request construction, canonical-window preservation and replay, direct and Cloud transports, automatic compaction lifecycle events, malformed provider state, provider ownership, format compatibility, and HTTP failure handling. ## Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content adheres to Zed's UI standards ([UX/UI](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) and [icon](https://github.com/zed-industries/zed/blob/main/crates/icons/README.md) guidelines) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable --- Release Notes: - Added: System messages are now sent through the `instructions` field in OpenAI Responses API requests.
jolutz
pushed a commit
to jolutz/zed
that referenced
this pull request
Aug 8, 2026
…ion (zed-industries#61370) # Objective Add explicit conversation compaction for OpenAI Responses API models, available through both direct OpenAI connections and Zed Cloud models. Keep finalized replacement context provider-neutral and separate from the lifecycle events emitted while automatic compaction is in progress. ## Solution - Add opt-in explicit compaction support to the `LanguageModel` trait. - Separate streamed `CompactionUpdate` lifecycle events from finalized `CompactedContext`. - Represent provider-native compacted context as an opaque, versioned state owned by the originating provider. - Construct compact requests through the same OpenAI request conversion used for completions, then narrow the request to fields supported by `/responses/compact`. - Preserve and validate the complete canonical replacement window returned by OpenAI. - Replay the replacement window before messages sent after compaction, without resending the superseded transcript. - Support explicit compaction through both the direct OpenAI provider and `CloudLanguageModel`. - Update automatic OpenAI and Anthropic compaction to use the same finalized context representation. - Reject empty, malformed, incorrectly versioned, and incorrectly owned provider state. The corresponding Cloud change adds the `/completions/compact` proxy route: zed-industries/cloud#3099. The downstream Delta UI integration is zed-industries/delta#1739. ## Testing - `cargo nextest run -p anthropic -p open_ai -p language_models_cloud` - `cargo check -p language_models --tests` - `cargo fmt --all --check` - `git diff --check` The focused tests cover request construction, canonical-window preservation and replay, direct and Cloud transports, automatic compaction lifecycle events, malformed provider state, provider ownership, format compatibility, and HTTP failure handling. ## Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content adheres to Zed's UI standards ([UX/UI](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) and [icon](https://github.com/zed-industries/zed/blob/main/crates/icons/README.md) guidelines) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable --- Release Notes: - Added: System messages are now sent through the `instructions` field in OpenAI Responses API requests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Objective
Add explicit conversation compaction for OpenAI Responses API models, available through both direct OpenAI connections and Zed Cloud models.
Keep finalized replacement context provider-neutral and separate from the lifecycle events emitted while automatic compaction is in progress.
Solution
LanguageModeltrait.CompactionUpdatelifecycle events from finalizedCompactedContext./responses/compact.CloudLanguageModel.The corresponding Cloud change adds the
/completions/compactproxy route: https://github.com/zed-industries/cloud/pull/3099.The downstream Delta UI integration is https://github.com/zed-industries/delta/pull/1739.
Testing
cargo nextest run -p anthropic -p open_ai -p language_models_cloudcargo check -p language_models --testscargo fmt --all --checkgit diff --checkThe focused tests cover request construction, canonical-window preservation and replay, direct and Cloud transports, automatic compaction lifecycle events, malformed provider state, provider ownership, format compatibility, and HTTP failure handling.
Self-Review Checklist:
Release Notes:
instructionsfield in OpenAI Responses API requests.