Kavor 1.4.0
Highlights
- Adds Grok as a CodingAgent provider, using an ACP client with configuration, interactive input, and session naming and catalog support through the ACP extension-method wire convention.
- Adds OpenCode as a CodingAgent provider, with an authenticated local-server lifecycle and session new, resume, fork, list, and naming support, including a Windows release install with no WSL fallback required.
- Adds a provider-picker Canvas palette tool so placing a CodingAgent node includes an explicit provider choice, with a shared press-vs-drag gesture helper reused across the palette.
- Renders Sixel and iTerm2 inline images in the embedded Terminal and CodingAgent PTY views, matching what the underlying process may already emit.
- Supports multiple specification roots per Workspace, with matching updates to the Specification Settings, Backlog panel, and folder tree so Specifications can be organized across more than one root.
Fixes
- Fixes an Onboarding handoff race where a lazy-loaded Workspace route could suspend and clear the Onboarding preparation flag, leaving the Canvas hydrated behind a stage Onboarding never released.
- Rolls back a provider session id an adapter invented but never confirmed when the Interactive PTY exits before startup readiness, so a first-launch failure can no longer leave a Node permanently pointed at a session the provider never created.
- Narrows the provider-launch environment guard to the two variables Kavor actually owns instead of the whole inherited ambient environment, and adds an explicit update-required provider startup outcome alongside the existing command-missing one, surfaced in the install overlay, toolbar, and node chrome.
- Persists a multi-node Canvas drag as one grouped move instead of separate per-node writes.
- Stabilizes deferred PTY presentation, login-shell environment resolution, and the xterm terminal-screen tracker.
- Fixes OpenCode CodingAgent nodes getting stuck showing Working forever when the provider's event transport drops a session's idle transition; Kavor now reconciles the real session status directly when that happens.
Installation
Download Kavor from https://download.agentkavor.com. The page detects the current platform and also exposes every available package. Existing direct installations can check for this release from Kavor's Software Update settings. No manual Workspace-data migration is required; Kavor backs up supported local databases before applying schema upgrades.
- Windows x64 uses the assisted per-User NSIS installer. The installer is currently unsigned, so Microsoft SmartScreen may require explicit confirmation.
- macOS 13+ provides separate arm64 and x64 DMGs. Builds are ad-hoc signed but not notarized; follow the download page's Gatekeeper instructions. Kavor-managed updates use the matching architecture-specific ZIP and expose an explicit coordinated restart after the cached artifact is revalidated. The manual download remains available at all times.
- 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
- Schedule Triggers require the Kavor runtime to be running, the machine to be awake, the User to be signed in, and the target session to be active. An occurrence missed while Kavor was not running is recorded and offered as an explicit manual run; it is never executed automatically on the next launch.
- Windows ARM64 and Linux ARM64 packages are not included until their native PTY, SQLite, process-containment, and packaged-runtime gates can run on matching CI environments.
- Windows direct downloads do not yet have an Authenticode publisher certificate.
- macOS packages do not yet have Developer ID signing or notarization. Gatekeeper may require manual confirmation,
and replacing an ad-hoc build may cause macOS to request access to
Kavor Safe Storagein Keychain again. - Microsoft Store distribution is not part of this release.