Synara 0.5.4 release notes.

Synara 0.5.4

• Review pull requests without leaving Synara — Browse, search, and filter pull requests across your projects, then open a complete review workspace beside the conversation.

  The new GitHub CLI-backed Pull Requests view groups work by involvement and state, supports project-scoped discovery, and opens summary, code, and timeline views with checks, reviewers, commits, file changes, and discussion context.

• Take action from the review workspace — Comment, merge, close, reopen, and pin pull requests while keeping the latest repository state close at hand.

  Mutations use shared cache coordination, single-flight refreshes, guarded optimistic state, and recovery paths so overlapping actions and refreshes remain predictable. Pinned pull requests stay easy to return to from the project workspace.

• Repository failures stay contained — One unavailable repository no longer prevents useful pull-request results from the rest of your workspace.

  GitHub CLI availability, authentication, repository discovery, partial-result errors, stale cached data, and retry recovery now have explicit states. Per-repository failures remain visible without discarding successful results.

• Send feedback from anywhere — Open the new feedback dialog from the command menu or with /feedback whenever an idea or problem comes up.

  Feedback is now a global workflow rather than a settings-only destination, with consistent command routing and a focused dialog that keeps the current task in place.

• Desktop windows reopen where you left them — Synara restores the previous desktop window size, position, and maximized state while keeping reopened windows on a visible display.

  Window state is persisted across launches and validated against the current monitor layout, avoiding off-screen restoration when displays have changed.

• Model and session behavior is more predictable — Agent sessions, transcript rendering, model discovery, and reasoning controls now stay aligned across more providers.

  Session orchestration and transcript rendering share a cleaner lifecycle, Pi custom-provider authentication follows auth.json semantics, Cursor transport-only variants stay out of the picker, and Grok reasoning-effort options match provider capabilities. The interface also adopts the system UI font more consistently.