Synara 0.6.4 release notes.

Synara 0.6.4

• Agents can use the visible browser — Let supported agents navigate and operate the same browser surface you can see, with tabs, snapshots, screenshots, input, dialogs, and workspace-safe file transfer.

  The browser bridge is provider-agnostic and session-scoped: it reuses Synara's visible Electron WebView, cookies, and authenticated state instead of creating a hidden browser. Agents get bounded semantic snapshots, trusted clicks, typing, key presses, scrolling, selection, dragging, waits, and page diagnostics, while navigation, target refs, timeouts, popup sign-in, uploads, and download approval boundaries stay explicit.

• Annotate the page before you ask — Select elements in the visible browser and send compact, redacted annotations with your message so an agent knows exactly what you mean.

  Annotations preserve bounded element role, name, text, selector, and page context, support multiple marks with a compact overflow row, survive drafts and transcript rendering, and keep exact-page affinity local. Untrusted page data is clearly separated from user instructions and document-only metadata is removed before provider injection.

• Choose how much autonomy each run has — Pick Approval required, Auto, or Full access when the selected provider and model support it, with clearer model, effort, and approval controls.

  Runtime mode is validated before dispatch, and automation or delegated work cannot silently escalate its privilege. Codex and Claude Code expose Auto only when capability is confirmed; unsupported or unknown capabilities fail closed to approval-required. The composer and model pickers now explain the effective mode and pending approvals more clearly.

• Steer live turns without breaking the transcript — Send guidance into a running Codex or Claude turn, or keep follow-ups queued, while the current task remains correctly attributed.

  Native steer calls travel through provider-aware command handling, runtime activity projection, and lifecycle fencing. Sent user messages, live assistant answers, child work, and terminal events stay attached to the right turn across late or replayed updates, interruptions, and provider restarts.

• Streaming conversations stay anchored — Long or fast responses no longer yank the viewport away from the point you are reading.

  Tail following now uses one shared anchor path across estimated and virtualized rows, sent-message reveals, and native browser end-space. New real transcript messages drive auto-follow; tool rows, buffering, measurements, and reconnect-only updates no longer impersonate user-visible message arrivals.

• Reconnects use less bandwidth and recover more state — Synara negotiates one authenticated connection, compresses large traffic, and resumes thread detail from a cursor when possible.

  A single handshake negotiates compatibility and permessage-deflate; delta-capable subscriptions replay from safe cursors with conservative snapshot fallback; precompressed web assets and cache headers speed first loads. Hydration also reads durable projections directly, retries missing snapshots after timed-out starts, and keeps provider notification drains alive until sessions settle.

• Open workspace tools from one right dock — A new launcher puts review, terminal, browser, files, side chat, and source control one click away without crowding the composer.

  Dock panes open at a stable half-shell split, keep live terminal state mounted when switching, and gate tools on the current project and repository. Missed draft promotions are recovered during event routing, so a message is less likely to disappear when the dock or task changes.

• Provider choices show their real capabilities — Model discovery and runtime menus stay useful across cold starts, Claude capabilities, and mixed provider sessions.

  Claude models can be discovered on a cold start, model and effort options use capability-aware ordering and labels, and thread hover cards expose the active provider and model context. Unknown provider update statuses no longer break self-update flows, and Antigravity returns a decision for inactive hook requests instead of launching Synara.

• Git workflows explain what needs attention — When a branch is behind upstream, Environment surfaces Pull before risky actions, and generated PR bodies can follow repository templates.

  Git action availability now uses one consistent upstream and working-tree state model. PR generation discovers applicable .github templates, removes boilerplate instructions, and asks the selected provider to fill the repository's own sections while preserving the fallback body when none exists.