Amplifier Unified 0.20.51

Resolve saved bundle IDs and report startup failures clearly

Changes

• Resolve uniquely registered bundle IDs case-insensitively when there is no exact registration or local bundle. Preserve exact aliases, paths and URLs; require an exact ID for ambiguous matches. New standalone IDs use lowercase with dashes.
• Provide an explicit metadata-only repair for saved Work chat references to work, preserving transcripts, model choices and customizations without starting workers or replaying saved messages. Report busy writers and conflicting or unreadable metadata rather than silently substituting a bundle.
• Retain private diagnostics for failures before worker startup and show actionable bundle-configuration guidance. Failed runtime controls settle as errors; background preparation reports unavailable instead of remaining in preparation indefinitely.

Amplifier Unified 0.20.50

Choose Work with Amplifier development tools by default

Changes

• Offer anchors, anchors-amp-dev, work and work-amp-dev by default in chat and workspace starters. Work · Amplifier development combines the Work profile with Amplifier ecosystem knowledge and tooling.
• Keep chosen defaults, custom source bindings, disabled bundles and existing histories unchanged. Work remains the fallback when no default is selected.
• Prepare bundle sources and dependencies on use, not eagerly during package installation. Component updates qualify the currently offered roots.

Amplifier Unified 0.20.49

Start workspaces with reusable setups and focused controls

High-impact changes

Workspace and chat controls moved out of global Settings

Workspace readiness, resource records and workspace bundle overrides are in Workspace → Details. Chat-specific Settings destinations now link to Chat details or Chat controls. Starter changes apply only to newly created workspaces; existing files and workspaces are preserved.

What to do: Open a workspace and choose Details for its controls. To try the new guidance and optional local Git setup, create a new workspace with the desired starter.

Changes

• Choose Blank, Development or Amplifier development when creating a workspace. Duplicate built-ins into custom starters in Settings → Workspaces → Manage starters.
• Offer the same registered root bundles in chat and starter controls: anchors, anchors-amp-dev and work, plus enabled standalone additions from Advanced settings.
• Create workspace-container guidance and bounded root working memory without replacing existing files. Project repositories remain independent child checkouts. Amplifier development initializes local workspace Git by default, without commits or a remote; duplicate the starter to turn this off.
• Keep global defaults in Settings. Manage workspace readiness, bundle overrides and external resource records in Workspace → Details, and chat-specific controls in Chat details/Chat controls.
• Let provided Markdown prose wrap naturally in viewers while preserving its structural lines and user-authored text.

Amplifier Unified 0.20.48

Start requested updates promptly and download components together

Changes

• Start eligible updates immediately after a manual check, retain Install requests made during a running check, and resume staged updates as soon as blocking work finishes.
• Download independent component checkouts concurrently with a bounded limit. Follow-up checks reuse recent availability results; new manual checks still refresh sources.
• Include recent check timings, server update state and the browser’s displayed state in copied or saved update diagnostics, without including private paths or conversation content.

Amplifier Unified 0.20.47

Update configured bundles and copy useful diagnostics

Changes

• Prepare only bundle profiles registered in current settings. Historical registry entries no longer appear as selectable profiles or block component updates with missing-bundle errors.
• Copy or save an update diagnostic report in one click, including update phases, timings, installed versions and source differences from the recorded worker installation. Reports exclude credentials, private paths and conversation content.
• Preserve the existing protection for locally changed worker dependencies. Runtime repair remains an explicit maintenance action.

Amplifier Unified 0.20.46

Prepare shared component generations and adopt updates between work

High-impact changes

Use shared component generations

Component updates now prepare the current app offerings together. Already running conversation workers keep their loaded version until their work can safely retire.

What to do: Let the included-components update finish once after installing this release. New work then uses the qualified generation automatically; application updates still require their normal restart.

Changes

• Prepare the currently offered app profiles together in one dependency installation, then check each profile in a fresh process. Historical chats and workspace combinations no longer multiply routine update preparation.
• Reuse indexed source inventories and coalesced availability checks. Proven catalog-data-only changes reuse a qualified runtime; code, dependency and configuration changes still receive isolated qualification.
• Share qualified component environments and exact source revisions across compatible conversation workers. Custom configurations prepare separately when first used, and conflicting requirements stop a candidate without changing the running environment.
• Make compatible component updates available to new workers immediately. Active workers finish on their existing generation and adopt the update after safe retirement; active voice, queued input, approvals and uncertain operations remain protected.
• Retain rollback and referenced generations, and reclaim only proven unused owned environments. Application updates still use the coordinated restart boundary. CLI caches and registries remain separate, and native history is preserved without replay.

Amplifier Unified 0.20.45

Save changed conversation records and reuse unaffected client views

Changes

• Persist admitted runtime-progress and inactive-payload changes as scoped records instead of serializing the whole app state. Keep complete checkpoints for unknown, global and topology changes.
• Reuse unaffected browser snapshots during scoped streaming updates while preserving private drafts, current revisions and previously delivered frames. Shared summary and navigation changes continue to invalidate conservatively.
• Keep an exact immutable payload reference for each committed conversation view. Restart reads the last committed payload rather than a newer presentation file left by a failed save.
• Preserve pending writer scopes and private client changes through SQL failures, failed presentation rollback and retries. Resource cleanup and reviewed deletion follow committed ownership without changing canonical transcripts or event logs.
• Verify the scoped streaming path at a 24,000-session library scale with two independent clients. Controlled callback CPU fell by 63–69%; peak process memory was essentially unchanged. Total live-app CPU, broader global writers and full recovery cost remain separate follow-up work.

Amplifier Unified 0.20.44

Explain update progress and retire inactive display payloads

Changes

• Show the current update batch, its component names, successful configuration checks out of the admitted total, and recently installed batches. New component changes detected between batches no longer look like the same stalled preparation.
• Keep earlier failed attempts distinct from current progress and preserve the original failure when cleanup cancels sibling checks. Validation, waiting for idle, and successful activation remain separate.
• Bound the retained event-index working set by count and measured payload bytes. Reuse unchanged indexes without changing event parsing, execution reconstruction or canonical history.
• Move eligible inactive conversation display payloads and inspection catalogs into verified app-owned resources after durable persistence. Keep connected and active work, drafts, approvals, provider configuration and receipts available; reload exact payloads on demand.
• Preserve inactive payload ownership through restart, resource cleanup and reviewed deletion. Retain borrowed mutable objects conservatively and refuse missing or altered resources rather than presenting empty history.
• Retain provider request-capture warnings in bounded browser details and align runtime test fixtures with the current admission and one-time environment preparation contracts.

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.

Amplifier Unified 0.20.42

Compact native conversation history in one request

High-impact changes

Compact native history in one request

This repair includes an updated context-management component. Existing conversation workers retain their loaded component code.

What to do: Let Settings → Updates finish installing included components, then use a fresh worker. Your saved chats remain available.

Changes

• Send the complete eligible conversation window in one native compaction request, preserving the selected model, current instructions and tool definitions. Native compaction never uses text-summary fragments.
• For providers that require text summaries, measure the complete summary request first and use a single summary when it fits. Split only when the provider budget, explicit source limit or unavailable measurement requires it.
• Keep native checkpoints, retained reminders and original saved history intact. Record why native compaction was selected or why the text-summary path was needed; healthy calls remain free of elapsed-time deadlines.