Install Kairo Code Desktop
Kairo Code is currently distributed as a controlled macOS Desktop preview. This official user manual follows the signed DMG experience from installation through everyday use, recovery, and safe removal.
Distribution availability
This site is a manual, not a download portal. Install Kairo Code only after your organization administrator provides an approved authenticated channel and the matching release record. There is no public download fallback.
Applications
- 01Mount DMG
- 02Move app
- 03Verify build
Before you install
The supported Desktop target is macOS on Apple silicon (arm64). The application includes its matching Java Host and browser runtime, so you do not need to install Java, Node.js, or a separate browser extension for the built-in Browser.
Before opening the DMG, confirm that the approved release record names:
- Kairo Code Desktop for macOS Apple silicon;
- the version and build identifier you received;
- a Developer ID signature and successful Apple notarization; and
- the DMG checksum or equivalent provenance identity.
If any field is absent or differs from the downloaded file, stop and contact your administrator.
Move Kairo Code to Applications
- Open the approved
.dmg. - Drag Kairo Code onto Applications inside the installer window.
- Wait for the copy to finish, then eject the Kairo Code installer volume.
- Open Applications and launch Kairo Code from there. Do not run the copy that remains on the mounted DMG.
For an approved Developer ID build, macOS should open the application normally. If macOS reports an unidentified or damaged application, do not disable Gatekeeper and do not run a quarantine removal command. Recheck the channel, checksum, signature, and notarization with your administrator.
Verify the running build
After Kairo Code opens, go to Settings → Advanced → About. Compare the displayed version, source revision, executable digest, and build date with the approved release record. The native Kairo Code → About Kairo Code panel confirms the application version, but the provenance fields in Settings are the stronger identity check.
Only begin real work after the installed application and approved record match.
Complete first launch
The first launch starts the bundled local Host and opens the Project launcher. Choose only the macOS permissions and workspace folders you expect:
- select Open Folder for a repository you are allowed to modify;
- add and test the model connection supplied by your organization;
- review the permission profile before the first Task; and
- leave Browser, Memory contribution, and external tool learning off until you intentionally enable them.
Kairo Code does not require access to every folder on your Mac. A prompt that does not match the workspace or action you initiated should be denied and investigated.
Update or roll back
Desktop shows an update only when an administrator has configured an approved release channel. Before applying it, finish or stop active Tasks and compare the proposed version with the channel's release record. Kairo Code stages and verifies the Desktop/Host pair before activation.
If a new version is unhealthy, open Settings → Advanced → About and use the offered rollback action when a verified previous pair is available. If no rollback action is shown, stop creating new work and contact your administrator instead of replacing individual application files.
Return to this manual
Use the persistent ? button at the lower-left of Desktop or the native Help menu:
| Desktop command | Destination |
|---|---|
| Kairo Code User Manual | Product overview |
| Install and Update Kairo Code | This page |
| What's New | Version notes |
| Troubleshooting | Desktop troubleshooting |
These links open product guidance only. They do not expose source code or authorize an installer.
Uninstall
Quit Kairo Code, move Kairo Code.app from Applications to the Trash, and empty the Trash when your organization permits it. Removing the application intentionally preserves Tasks, settings, Skills, Plugins, and local evidence so reinstalling does not silently destroy work.
If you also need to erase product data, permanently delete sensitive Tasks from Kairo Code first, then follow your organization's approved data-removal procedure. Do not manually remove individual database, Browser checkpoint, or Memory receipt files.
Next step
Continue to Your first Task.