Amplifier Unified 0.20.43

Resume compaction and speed up component updates

High-impact changes

Apply compaction recovery and provider improvements

This release includes app, provider and context-management repairs. Existing conversation workers retain the component code they already loaded. Request recording is optional and off by default.

What to do: Let Settings → Updates finish installing included components, then use a fresh worker for existing chats. Saved history remains available and work is not automatically replayed.

Changes

• Resume completed text-summary work after an interruption instead of repeating paid summaries. Save progress between completed parts, prevent hidden summary continuations, and check whether the complete history fits before making a native compaction request.
• Let healthy provider calls continue without an implicit elapsed-time deadline. Preserve explicit limits and cancellations, and retain accurate output-limit, usage and request evidence across the updated Microsoft providers.
• Run automatic naming periodically and quietly during ongoing work. Regenerate a chat name alongside active work while protecting later manual edits.
• Add an optional Advanced diagnostics setting to record future provider requests, with credential redaction and capture limits. Existing calls cannot gain request data that was never recorded; some SDKs expose only a request summary.
• Offer explicit ChatGPT Codex and Plan connections with Codex as the default. Preserve configured identities, clean up abandoned sign-in candidates safely, and explain when Plan cannot support a bounded test message.
• Clear reviewed chat and workspace error markers while preserving history, current failures, pending approvals, required questions and other active obligations.
• Reduce repeated update checks, source copies and module installations. Reuse exact downloaded Git revisions while retaining local edits, rollback receipts and fresh dependency resolution for each new preparation attempt.
• Group equivalent update sources into one row, disclose their cache and package roles, and sort source lists alphabetically. Distinct branches, revisions, update tiers and status remain separate.
• Keep Unified bundle registrations and downloaded remote caches independent of the CLI, while continuing to share configured settings, keys, native chat history and explicitly selected local resources.
• Show source storage information in update details and retire only proven, unreferenced app-owned component generations after successful activation. Keep active, previous, pending, modified and uncertain generations for recovery.