Skip to content

Installation ​

Choose your platform: macOS Apple silicon, Windows x64, or Linux x64 / ARM64. Computer Use and AppShots are macOS-only.

Install on macOS ​

  1. Open Downloads and choose the macOS DMG for Apple silicon.
  2. Open the DMG and double-click Korus. It installs in Applications and launches. If an installed copy needs replacing, confirm Replace; your chats and settings are kept.
  3. If Korus asks you to use Finder, choose Open Applications, drag Korus there from the DMG, and approve the installation in Finder. Then open Korus from Applications.
  4. The first-run screen checks your coding engines. Detected engines offer Connect, with Customize for engines that support separate setups. If one is missing, use Install and follow its setup flow; the refresh icon rechecks detection.
  5. Check your engine's setup before connecting it. Follow the steps below, then open a repository.

Install on Windows ​

Choose the Windows x64 installer from Downloads, run it, and launch Korus. The Windows build is unsigned, so Windows may display a security warning. Verify that the file came from the official GitHub release before proceeding. A ZIP is also provided for manual extraction.

Install on Linux ​

Choose x64 or ARM64 to match your system, then select the DEB, RPM, or ZIP format from Downloads. Use your distribution's package manager for DEB or RPM files; extract the ZIP for a manual installation. Korus does not infer Linux architecture from your browser.

Install on iPhone ​

Download Korus Mobile from the App Store on an iPhone running iOS 26 or later. It connects to Korus on your Mac, Windows, or Linux computer so you can continue conversations, follow Missions, review changes, and respond to your agents away from your desk.

Enable mobile access in Settings → Connections on the computer, pair your phone, and approve it on the desktop. Keep the computer awake, running Korus, and connected to the internet. See Continue from your phone for pairing and connection settings.

Updates ​

Packaged macOS and installed Windows apps receive stable releases through the app's updater. Linux, portable Windows, and prereleases use manual downloads from GitHub Releases. Choose the build for your platform and architecture.

Choose separate or existing provider setup ​

Korus uses your existing Codex and Claude Code setup by default, including their sign-in. To keep Korus chats separate, click Customize beneath the engine on the first-run screen and choose Separate Korus chats. Saved setup choices are preserved.

ChoiceUse it when
Separate Korus chatsYou want Korus's chats and provider sign-in kept in a separate setup environment.
Use existing setupYou want Korus to use the provider environment already configured on this computer.

Choose independently for Codex, Claude Code, and Antigravity. Cursor uses the existing Cursor CLI setup; it does not offer a separate home. Selecting an existing setup or signing in to one engine does not configure or authenticate the others.

Follow the provider setup overview before changing an existing setup. It explains skills and plugin sharing, the selected provider location, and what happens to Korus conversations when you switch locations later.

Connect at least one engine ​

Korus does not include a separate model subscription. Connect a provider account with access to the engine you want to use.

A separate Claude Code installation is optional when Korus's bundled runtime is available. On macOS, Codex can use ChatGPT's runtime if there is no standalone CLI. These runtime choices do not replace provider sign-in or grant model access.

  1. If your chosen engine already shows Connected, no sign-in is needed. Otherwise, select Connect and complete its authentication steps.
  2. Confirm the engine is connected and enabled. The first-run Continue action becomes available when at least one installed engine is connected and enabled; additional engines are optional.
  3. Select Continue.

Use the provider guides, including Antigravity setup, for the engine you choose. A detected installation alone does not establish that its selected setup environment is signed in.

Connect GitHub or GitLab, or skip it ​

If GitHub CLI (gh) is authenticated to github.com on this computer, Korus detects that access. Choose Connect GitHub for faster direct access, or Use GitHub CLI to continue with your existing CLI sign-in. Without authenticated CLI access, choose Skip for now to start with a local folder. You can connect later in Settings → Integrations.

GitLab.com has its own connection choice in the same step, including authenticated GitLab CLI (glab) access. You can connect either or both services before continuing.

GitHub and GitLab authorization are separate from your coding provider's account. You can run a local repository task without connecting either service.

Open a working folder ​

In the empty workspace, choose Existing folder or repository… to open a checkout already on disk. The same start-work menu offers a new project, a GitHub or GitLab repository, or a repository URL.

For a first task, choose a small local repository whose branch and existing changes you understand. Continue with the quickstart.

Next step ​

Follow the quickstart. If launch or authentication fails, start with Troubleshooting.