Dyad v1.16.0: Fix duplicate compaction summaries after chat reload (#4630): Summary Reloading a chat after mid-turn compaction shows the same
The official v1.16.0: Fix duplicate compaction summaries after chat reload (#4630) release documents a concrete integrations change. This update explains what changed from v1.16.0-beta.1, who should reassess the product, and what to verify next.
- What changed
- The official v1.16.0: Fix duplicate compaction summaries after chat reload (#4630) release documents a concrete integrations change. This update explains what changed from v1.16.0-beta.1, who should reassess the product, and what to verify next.
- Who is affected
- Evaluators, administrators, and workflow owners using Dyad where integrations requirements affect adoption or deployment.
- What to do now
- Review the official v1.16.0: Fix duplicate compaction summaries after chat reload (#4630) notes, test the affected integrations workflow, and update the adoption decision if the result changes product fit.
The material change
Previously: {{agentName}} v1.14.0-beta.1 documents this product change: Full release notes: https://www.dyad.sh/docs/releases/1.14.0-beta.1 What's Changed Stabilize catalog E2E and Windows unit tests by @keppo-bot[bot] in #4413 feat: create Supabase projects from an app's database connector
Now: Dyad v1.16.0: Fix duplicate compaction summaries after chat reload (#4630) documents this product change: Summary Reloading a chat after mid-turn compaction shows the same compaction twice: once inside the assistant reply and again at the bottom as a separate message.
This update covers the v1.16.0: Fix duplicate compaction summaries after chat reload (#4630) release notes and does not infer behavior beyond the official release description.
What users should reconsider
The move from v1.16.0-beta.1 to v1.16.0: Fix duplicate compaction summaries after chat reload (#4630) introduces a documented change that may alter operational compatibility.
The release has a versioned first-party source, so teams can verify the exact scope instead of relying on a generic monitoring excerpt.
Verify the affected workflow
- Review the official v1.16.0: Fix duplicate compaction summaries after chat reload (#4630) notes, test the affected integrations workflow, and update the adoption decision if the result changes product fit.
- Open the official source and verify the current product state.
- Review the current Agent Profile and affected Decision before acting.
Source-Backed does not mean execution-verified and does not establish comparative rank.
What was recorded before
{{agentName}} v1.14.0-beta.1 documents this product change: Full release notes: https://www.dyad.sh/docs/releases/1.14.0-beta.1 What's Changed Stabilize catalog E2E and Windows unit tests by @keppo-bot[bot] in #4413 feat: create Supabase projects from an app's database connector
What is known now
Dyad v1.16.0: Fix duplicate compaction summaries after chat reload (#4630) documents this product change: Summary Reloading a chat after mid-turn compaction shows the same compaction twice: once inside the assistant reply and again at the bottom as a separate message. This update covers the v1.16.0: Fix duplicate compaction summaries after chat reload (#4630) release notes and does not infer behavior beyond the official release description.
Accepted Change accepted:4314fc8c481f70c2e57969857b95873f · Agent Fact fact:4314fc8c481f70c2e57969857b95873f · Last verified 2026-09-18Dyad official releases
Published by Dyad. Evidence state remains Source-Backed; this is not execution verification.
Open official source →