Skip to documentation
Current releaseReleased October 16, 2026GitHub Release

Kavor 2.0.0

Highlights

  • Your agents, now on WhatsApp. Talk to your local agents from a personal chat or a dedicated group for each Workspace. Open Channels setup in the header to link your account; Workspace Channels appears after linking, and settings save automatically.
  • Kavor Chat brings human-to-agent conversations into the Workspace. Select a Workspace and CodingAgent, follow progress, answer questions, and exchange attachments while keeping the conversation's context.
  • CodingAgent communication now supports provider-native submission, after-turn delivery, and explicit interruption where permitted. Delivery respects Connection Guardrails and preserves human drafts; connected agents can also read completed peer-session turns through bounded, paginated history.
  • Connected agents can control live WebBrowser tabs outside the visible Canvas. Browser settings now retain explicit Start and Shutdown choices and audio muting without deleting saved tabs or shared site data.
  • Refreshes desktop typography with Inter and Geist Mono, refines application artwork, and restores transparent macOS application icons.
  • Starts supporting processes on demand and releases inactive resources while preserving persisted Workspace, Terminal, CodingAgent, and Browser state.

Fixes

  • Preserves native CodingAgent startup options, including explicit model, permissions, session, and working-directory arguments, without silently replacing the User's choices.
  • Corrects Grok turn completion and qualified passive session reads, and improves native message-delivery correlation and notice acknowledgement across Workspace windows.
  • Surfaces native CodingAgent questions and includes the originating Workspace in operating-system notification titles, making parallel Workspace activity easier to identify.
  • Improves WhatsApp pairing, personal-chat and group setup, context selection, reconnection, and attachment transfers. Motion Photo requests retain their original content and correlation across native replay.
  • Keeps Chat and WhatsApp command, status, question, cancellation, and error feedback consistent, with explicit handling for outdated selections and unavailable quoted messages.
  • Preserves Browser shutdown intent and live tab state across UI lifecycle changes, and improves PTY and supporting-process cleanup.

Installation

Download Kavor from https://download.agentkavor.com. Existing direct installations can check for this release from Software Update settings. Workspace database upgrades run through Kavor's backed-up migration path.

  • Windows x64 is available from Microsoft Store or as the assisted per-User NSIS installer. Microsoft signs and updates Store installations. The direct installer remains unsigned, so Microsoft SmartScreen may require explicit confirmation.
  • macOS 13+ provides separate Apple Silicon and Intel DMGs signed with Kavor's Apple Developer ID and notarized by Apple. Automatic updates use the matching architecture-specific ZIP and retain the manual DMG fallback.
  • Linux x64 provides AppImage and DEB packages. AppImage supports Kavor-managed updates with an explicit coordinated restart; DEB updates are installed manually from the download page.

Known limitations

  • An OSC 8 Terminal hyperlink printed on a line already under the pointer may require moving the pointer to another line and back before opening. This upstream xterm hover-cache limitation remains in this release.
  • The production dependency audit reports unresolved upstream denial-of-service advisories for braces and sprintf-js. These dependency versions were already present in Kavor 1.7.1. Recursive Workspace watching disables glob expansion for the braces path; that is a mitigation, not a patched dependency.
  • WhatsApp requires a linked account, network access, and Kavor running on the desktop. Its linked-device integration is not Meta's hosted WhatsApp Business API; WhatsApp account restrictions remain controlled by Meta.
  • Kavor's dedicated shared Browser Profile accepts every server certificate to support local development. A hostile network can therefore impersonate sites opened in that profile, including sites where the User signs in. The Kavor application session retains Chromium's normal certificate verification.
  • WebBrowser Nodes do not reuse the User's external Chrome profile, extensions, history, or cookies. Deleting a Node does not erase shared site data; global Kavor settings provide explicit cache, cookie, and site-data clearing.
  • Cross-site frames isolated into another Chromium process are reported as omitted and cannot be controlled through the guest-scoped security boundary.
  • Windows ARM64 and Linux ARM64 packages are not included. Windows direct downloads do not yet have an Authenticode publisher certificate; Microsoft Store packages are signed by Microsoft. Store availability may follow the direct stable release after Microsoft's independent certification completes.
Last reviewed Oct 16, 2026Verified with Kavor 2.0.0Share documentation feedback