Bug: Compact and Continue always fails with COMPACTION FAILED error; detai...

[RaudrSkol]

Summary

Compact and Continue always fails with COMPACTION FAILED error; details tab unresponsive

Environment

• Maestro version: 0.16.16
• Operating system: Windows (Windows 10 Home, 10.0.26200)
• Install source: Packaged build (release build or locally packaged)
• Agent/provider involved: Not provided
• SSH remote execution: Not provided

Steps to Reproduce

1. Open any assistant session (Claude or Codex) with enough context to trigger compaction. 2. Click 'Compact and Continue'. 3. Observe immediate failure toast in bottom-right corner. 4. Attempt to click the details tab that appears.

Expected Behavior

Compact and Continue should successfully compact the context, allowing the conversation to continue. If it fails, the referenced details tab should be clickable and show actionable error information.

Actual Behavior

Compact and Continue immediately fails with a toast notification: 'COMPACTION FAILED - Failed to compact context. Check the tab for details.' The details tab that appears is completely unresponsive — clicking it does nothing and it shows no content.

Additional Context

Issue reproduces on both Claude and Codex assistants. The double failure (compaction itself + broken details tab) means there is no way for the user to diagnose or work around the problem.

Screenshots / Recordings

[pedramamini]

Thanks for the detailed report — the screenshot makes the failure mode obvious.

I think we have a fix in #950. Two things were going wrong here:

1. The toast says "Check the tab for details" but no tab actually renders the error — the per-tab progress overlay only shows while compaction is running, so once it failed the details disappeared. That's why clicking around did nothing.
2. A bare catch in the summarizer was wrapping the real error in a generic "Context summarization failed" string, so even Sentry was getting useless data and there was no way to tell why it was failing for you.

The fix preserves the underlying error (e.g. "Agent X is not available", a spawn error, etc.) and puts it directly in the toast — so next time it fails you'll see the actual cause. That should let us figure out what's specifically breaking on your Windows 10 setup, since this isn't reproducible for me.

Would you mind giving #950 a look and letting me know if the surfaced message points to a more specific cause when it lands?