What's new
This page summarizes changes that affect how you use Kairo Code. Your administrator may stage releases on a different schedule.
Release status
- Candidate version:
0.2.0 - Status: Unreleased private candidate
This is a qualification snapshot, not a public release, general-availability, production-readiness, or acquisition claim. A build is authorized only when your organization supplies approved release metadata that matches the installed artifact.
0.2.0 / Unreleased private candidate
This candidate summary was updated in August 2026. The calendar date is documentation context; it is not a build identity or evidence that the candidate has been released.
Smoother Task continuity
Steering messages, reviews, cancellation, and recovery now stay attached to the same Desktop Task more consistently. Invalid requests are rejected before work begins, while valid Tasks remain resumable after a client disconnect or restart. A background Subagent's completion becomes visible only after its completion result is durably recorded.
Safer Chrome recovery
Paired-Chrome control now keeps a durable receipt before a click, type, navigation, or other page effect. If Kairo loses the acknowledgement, it leaves the old result explicitly unknown and asks you to inspect a fresh snapshot before deciding what to do next; it does not blindly replay the action. This is a recovery fence, not a guarantee that an external website applied an action only once. The bundled extension protocol changed in this release, so reload the extension folder and pair Chrome again after upgrading.
The built-in Agent Browser also keeps its execution lane closed until a timed-out native action has really settled. When its bounded command or session authority is full, Kairo refuses new page effects instead of forgetting an older uncertain result.
Safer Plugin updates
Plugin installation now presents the version and capability changes for review before activation. If activation fails, Kairo Code keeps or restores the last usable installation. Running Tasks keep their existing capability snapshot; start a new Task to use an activated update. Installing a second Plugin with the same declared name now returns a clear conflict instead of a generic server failure.
Privacy-first Memory controls
Memory recall, contribution, and learning from tool-assisted Tasks are independent choices and are off by default. Changes apply to new Tasks, and the device-local choices reset when the signed-in or paired identity changes. The default file store now rejects a damaged or oversized scope as a whole instead of silently presenting a partial Memory list. Validated reads and mutations are serialized across cooperating processes sharing its real directory, while the supported Kairo Code topology remains one Host process because management cursors and other authorities are instance-owned.
A clearer user manual
The public manual now follows only the Desktop/DMG journey: installation, Projects, model connections, permissions, daily workflows, customization, and recovery. Settings paths and action names match the current application, and engineering notes never enter public search by default.
Check your version
The candidate described on this page uses semantic version 0.2.0. Open Settings → Advanced → About in Desktop. A matching version alone does not establish build identity or authorization: compare the running source revision, executable digest, and build date with the approved provenance record supplied with the DMG.
For update and rollback instructions, see Install Kairo Code.