Bump agents-ui, remove the need to force refresh the widget when the …

[sarah-inkeep]

…headers change now that the widget is fixed

[changeset-bot]

🦋 Changeset detected

Latest commit: 09933d0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 9 packages

Name	Type
@inkeep/agents-manage-ui	Patch
@inkeep/agents-manage-api	Patch
@inkeep/agents-run-api	Patch
@inkeep/agents-cli	Patch
@inkeep/agents-core	Patch
@inkeep/agents-manage-mcp	Patch
@inkeep/agents-sdk	Patch
@inkeep/ai-sdk-provider	Patch
@inkeep/create-agents	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
agents-docs	Ready	Preview, Comment	Jan 7, 2026 8:10pm
agents-manage-api	Ready	Preview, Comment	Jan 7, 2026 8:10pm
agents-manage-ui	Ready	Preview, Comment	Jan 7, 2026 8:10pm
agents-run-api	Ready	Preview, Comment	Jan 7, 2026 8:10pm

[claude]

Claude finished @sarah-inkeep's task —— View job

---

PR Review: Bump agents-ui and Remove Widget Force Refresh Logic

Todo List

• Examine changed files to understand the scope of changes
• Analyze version bump implications across packages
• Review removal of force refresh logic
• Check for architectural consistency and best practices
• Provide comprehensive feedback on system design implications

---

Summary

This PR removes a React performance anti-pattern (forced component remounting via dynamic key props) after upgrading to @inkeep/agents-ui v0.15.6, which presumably fixed the underlying widget state issues that necessitated the workaround.

Key Changes Analysis

1. Force Refresh Logic Removal ✅ Good Change

The PR removes React key props that were causing component remounts:

Before:

<InkeepSidebarChat
  key={JSON.stringify(dynamicHeaders)}  // ← Removed: Forced remount on header changes
  // ... other props
/>

<ChatWidget
  key={JSON.stringify(customHeaders)}   // ← Removed: Forced remount on header changes
  // ... other props
/>

Why this is good:

• Eliminates expensive component remounts that destroy and recreate entire component trees
• Removes JSON.stringify() performance overhead on every render
• Allows proper React reconciliation and internal state preservation
• Improves user experience by maintaining scroll position and form state

2. Version Coordination ✅ Well Executed

All packages consistently updated to @inkeep/agents-ui ^0.15.6 across the monorepo.

---

Architectural Review

✅ Strengths

1. Proper Root Cause Fix: This addresses the underlying issue in the widget library rather than maintaining workarounds in consuming code

2. Clean State Management: The components now rely on proper prop updates rather than forced remounting:

   • dynamicHeaders are passed directly to the headers prop and React will efficiently update only what changed
   • customHeaders flow through props naturally without state loss

3. Monorepo Coordination: Consistent version updates across all packages prevents version mismatches

⚠️ Areas for Consideration

1. Rollback Strategy: If issues arise with the new widget version, consider:

   • Having a feature flag to temporarily re-enable the key-based remounting
   • Documenting the specific issue that was resolved in v0.15.6 for context

2. Testing Implications: The behavior change warrants thorough testing:

   • Verify that header updates still trigger proper widget behavior
   • Test edge cases like rapid header changes or malformed headers
   • Ensure conversation context is preserved appropriately

3. Performance Monitoring: Since this affects core widget rendering:

   • Monitor for any performance regressions
   • Watch for widget state inconsistencies that the forced remounting was masking

🔍 System Design Observations

1. Header Flow Pattern: The architecture properly separates concerns:

   • CopilotContext manages dynamic headers from feedback flows
   • Playground manages custom test headers
   • Both flow through to widgets via props (not forced remounting)

2. State Preservation: Components can now maintain internal state across header changes, which is typically the desired behavior for chat widgets.

---

Recommendations

1. ✅ Approve: This is a solid architectural improvement that removes technical debt
2. Test Coverage: Ensure E2E tests cover header update scenarios
3. Documentation: Consider documenting the header flow architecture for future developers
4. Monitor: Watch for any edge cases in production where the old forced-refresh behavior was actually masking issues

This change represents good engineering practice: fixing root causes rather than maintaining workarounds, improving performance, and following React best practices.

---

[github-actions]

🔎💬 Inkeep AI search and chat service is syncing content for source 'Inkeep Agent Framework Docs'