Install, update, and run Kaidera OS

Commercial macOS package

Commercial Apple-silicon customers install one versioned macOS Installer package from the Kaidera website. The package installs Kaidera OS Operator; the Operator then completes dependency setup and stages the matching managed runtime.

• Supported platform: Apple silicon on macOS 14 or later.
• The commercial package is hosted on kaidera.ai and is not distributed through GitHub.
• Use only the package and release metadata linked from the official macOS download page.
• Open-source and internal-development editions have separate channel-specific instructions.

What installation creates

The Operator stages the managed Kaidera OS runtime, starts local services, installs the LaunchAgent, and verifies health and admin authentication before reporting success.

• Kaidera OS Operator in /Applications and the menu bar.
• A managed runtime under ~/Library/Application Support/Kaidera OS/.
• Cortex services for memory and project state.
• An app database for settings, project autonomy flags, worker overrides, and run state.
• A LaunchAgent that starts and supervises the local console.

Running the app

Use Kaidera OS Operator to open the console or run Install or Repair. The console is the local operator surface for Dashboard, workers, Dispatch, Runs, Settings, and Help. Do not expose the local console directly to the public internet.

Activation and trial

The nine-day commercial trial starts only after Docker, Cortex, the console, launchd, and admin authentication checks all pass. Activate under Settings > License with your Kaidera Platform email, password, and MFA code when prompted.

• Kaidera OS stores the resulting narrow license session and signed grant, not the password or MFA code.
• The unlicensed or expired floor is 1 project, 1 team, 4 AI workers, and 1 user.
• Advanced features, Manifold access, and BYOK providers require signed entitlements.

Updates

Use Check for Updates in Kaidera OS Operator to compare the running and available versions. Use Apply Update only after reviewing the offered version and allowing active worker runs to finish.

• The Operator reports the current version, latest version, update availability, and source.
• Apply Update is blocked while worker runs are active so an update cannot interrupt in-flight work.
• After an update, confirm the Operator reports the expected version and healthy services.
• Use Install or Repair if dependency or health checks do not recover normally.

Repair and recovery

Reopen Kaidera OS Operator and run Install or Repair after an interrupted setup or unhealthy dependency. Setup resumes without starting the commercial trial until all required gates pass.

• Install transcript: ~/Library/Logs/Kaidera OS/install.log.
• If Docker is installed but not ready, open Docker Desktop, wait for docker info to succeed, and retry.
• Keep the managed runtime out of Downloads, Desktop, Documents, cloud-synced folders, and removable volumes.
• Contact [email protected] for commercial installation or licensing support.

Troubleshooting install issues

Use the Operator transcript and health state to identify first-run failures before changing the managed runtime.

• For a Python download failure, check HTTPS and proxy access to the pinned uv distribution source.
• If the console does not open, inspect the install transcript and local Cortex logs under the managed runtime.
• If port 8765 is occupied, stop the owning service before running repair; the installer does not kill unrelated listeners.
• For license login failures, confirm network access, credentials, and the current MFA code.