Synara 0.8.0 release notes.

Synara 0.8.0

• Work with Devin from the same Synara workspace — Devin CLI joins Synara as a first-class ACP provider with its own models, commands, modes, usage, attachments, and MCP configuration.

  Synara can start and resume Devin ACP sessions, discover the models and slash commands exposed by the installed CLI, switch Plan mode, compact long conversations, attach files and images, pass compatible MCP servers, and show account usage. Authentication remains owned by Devin through devin auth login or its supported API-key environment variables, and provider capabilities are gated so unsupported active-turn steering is never implied.

• Give any capable provider the live browser tools — WebMCP browser tools are now provider-neutral instead of being tied to one agent runtime.

  Browser sessions expose the same bounded, task-owned WebMCP surface to supported providers, with consistent tool discovery, invocation, timeouts, result shaping, tab ownership, and lifecycle cleanup. This keeps browser work attached to the correct task while allowing more agents to inspect and operate the page Synara is already showing.

• Find anything inside a long conversation — Press Cmd/Ctrl+F to search the current transcript from a compact floating panel.

  The search walks real transcript messages, highlights matching text, reports the active result and total count, supports previous/next navigation and keyboard shortcuts, and follows matches without confusing tool-only rows with new assistant output. Closing the panel clears the temporary highlights without changing the conversation.

• Models, sidebars, and live replies react faster — A focused performance pass reduces model-loading delay, sidebar work, toggle churn, and streaming update cost.

  Available models are ready sooner, sidebar projections do less repeated work, visibility changes avoid unnecessary updates, and assistant text follows a simpler live-output path. Auto-scroll now responds to real transcript messages rather than buffering, reconnecting, approvals, or tool-only activity, which avoids feedback loops and unwanted jumps while work is merely pending.

• Queued follow-ups wait, dispatch, and recover predictably — Follow-ups no longer race the turn ahead of them or strand work when a task is in the background.

  Synara holds a queued follow-up until the previous turn has actually started, promotes work for backgrounded tasks, preserves preview contents while capacity is constrained, resumes from the durable cursor after an idle stop, and prevents duplicated streamed replies. Reconnect and settlement paths converge on the same turn instead of replaying visible text twice.

• Database upgrades fail safely and explain recovery — Schema migrations now verify runtime identity, ask before risky recovery, and keep source builds isolated from installed app data.

  A source checkout uses its own development home by default instead of silently opening Stable or Canary state. Migration startup verifies that the launcher and database belong together, creates recoverable backups, records recovery state, and presents deliberate restore or retry choices when an upgrade cannot complete. Existing Stable, Canary, and explicit home-directory behavior remains intact.

• Provider state is controlled by the server and visible in context — Settings, usage, context changes, update notices, and enabled-provider behavior now agree on what the runtime can actually do.

  Disabling a provider now prevents server lifecycle execution instead of only hiding it in the interface. Usage is available for every enabled provider Synara can verify, provider-driven context changes appear in the conversation, routine lifecycle hooks stay out of the transcript, and update notices recover when availability checks overlap or temporarily fail.

• Side chats keep their place and relationship — Parent-linked side chats now survive refreshes and expiry without losing the pane you were working in.

  Side-chat leases and parent relationships are stored durably, docked panes restore against the correct task, and archiving or unarchiving no longer discards an active lease. Expired transient state is reclaimed without confusing a regular child task for a disposable side chat.

• Arrange the sidebar around your workflow — The main navigation groups can now be reordered and keep that order across windows and restarts.

  Drag the configurable sidebar destinations into the order that suits you. The preference synchronizes through shared local storage, tolerates additions and older saved values, and preserves sensible defaults when stored data is incomplete or invalid.

• Files open, reveal, copy, and preview more reliably — Edited-file cards and workspace references have clearer actions and better path handling.

  macOS users can reveal a file in Finder, every platform can copy its path, and Open actions are separated from file management. Missing relative references no longer become misleading chips, valid absolute paths render as badges, dot-prefixed images and attachments are accepted, preview contents survive constrained queues, and numeric PDF destinations resolve to the intended page.

• Kilo Code data moves safely to OpenCode — The retired Kilo Code provider has been removed, with existing Kilo tasks and preferences migrated to OpenCode.

  The database migration preserves provider sessions and task history while translating the provider kind. Follow-up compatibility handling also moves favorite providers and saved editor-tab state, so older installations do not retain broken Kilo selections after upgrading.

• Git, terminal shortcuts, and task metadata stay attached — Pull-request attribution, creation time, terminal numbering, and final replies now resolve against the correct task.

  Pull requests are attributed to the owning thread rather than a neighboring checkout, created-at ordering remains stable, numbered terminal shortcuts select the intended tab, and the final assistant response remains self-contained after segmented or folded output. Factory Droid can also generate Git commit and pull-request text through the shared action flow.

• Paths, networks, payloads, and credentials fail closed — A broad boundary audit closes prototype, path, byte-limit, loopback, retry, and temporary-credential edge cases.

  Untrusted object keys cannot mutate prototypes, Windows drive-relative paths are rejected while drive roots remain valid, UTF-8 limits count bytes without splitting characters, IPv4-mapped addresses cannot bypass network policy, Retry-After values are validated and bounded, empty streamed chunks settle correctly at limits, and provider credential files use isolated temporary locations.

• Desktop updates and platform paths are safer — Electron, backend shutdown, Windows home paths, and source-launch identity received release-focused fixes.

  Electron is upgraded to 43.4.1 to include the fix for CVE-2026-70608. POSIX desktop updates now shut the backend down gracefully before replacement, Windows home paths abbreviate consistently, and source validation uses the working directory only when no stronger launcher digest is available.

• Provider resumes, compaction, and versions keep their identity — Replay gates and exact provider metadata prevent stale lifecycle work from appearing as new activity.

  ACP load replay is suppressed until the restored session is ready, native resume is gated by the provider's real capability, Claude Auto variants match exact context limits and fail closed, compaction refreshes usage from the new boundary, long-message pagination is lossless and Unicode-safe, and prerelease provider versions retain their complete identifiers.