Synara 0.5.5 release notes.

Synara 0.5.5

• Antigravity joins Synara — Connect the Antigravity CLI as a first-class coding agent, with discovered models, reasoning controls, streaming activity, approvals, and resumable conversations.

  The new provider adapter covers installation and authentication guidance, model and effort discovery, session creation and resume, tool and plan events, permission requests, usage reporting, cancellation, and restart recovery. Synara also includes dedicated Antigravity branding throughout provider setup and selection.

• Live turns settle cleanly — Working indicators and streamed turn chrome no longer linger after the underlying provider session has already finished.

  Turn settlement now follows the owning session lifecycle, while WebSocket RPC requests resolve or reject across close, timeout, send failure, and reconnect paths. This keeps pending UI state from becoming stuck during partial streams or interrupted connections.

• Active chats stay lighter — Conversation updates do less repeated reconciliation work, keeping busy transcripts and sidebar-driven changes more responsive.

  Chat state now avoids redundant scans and projections during live updates, bundled theme seeds reset consistently, and common transcript behavior remains on the simpler rendering path without introducing new measurement loops.

• Dropped paths become reliable mentions — Drop files and folders whose names contain spaces or parentheses into the composer without losing or mangling the path.

  Desktop path payloads are parsed and normalized through shared composer logic, then preserved as mentions across chat and Kanban task creation. Focused coverage includes encoded paths, multiple drops, punctuation, send normalization, and unsupported payloads.

• Provider failures stay contained — A failed Cursor model refresh no longer takes down the model picker or discards usable choices from other discovery sources.

  Model-catalog queries retain successful and cached data when one Cursor discovery path fails, while pull-request data is coalesced through shared list logic and picker popups use a unified interaction model. Diff headers now use Synara's own visual chrome for a more consistent workspace.