Set up KalCode on Windows or macOS

Download the official desktop app

Start on the official KalCode download page. It lists every currently published Windows and macOS build, along with its version, file size, signature state and SHA-256 checksum. Choose the package for your operating system, open it and complete the normal installation flow. If a platform has no public build yet, the download page says so rather than sending you to an unofficial file.

KalCode is a desktop workspace. Your project files and coding-agent terminals run on your computer, so choose a machine where you already do development work and have the toolchains your project needs.

Connect Claude Code, Codex, Cursor or Gemini CLI

KalCode supports all four current providers: Claude Code, Codex, Cursor Agent and Gemini CLI. Install the provider's official CLI first. In KalCode, open More, choose Providers, then open Accounts, add an account and choose Sign in. KalCode starts that provider's own sign-in flow; the provider keeps the credentials and remains responsible for its subscription, usage limits and approvals.

You can connect more than one account when the provider supports isolated profiles. Read Provider accounts and native tools for the current behavior of each CLI. KalCode does not supply a shared AI account or silently move an agent to another one.

Open your first project

Go to Code and choose Open folder. Select the root folder of the project you want to work on. KalCode calls this a workspace: its terminals, agents, files and activity stay grouped around that folder. A Git repository is recommended, and it is required later if you want isolated worktrees for parallel agents.

Launch one coding agent

Choose New agent in Code to start the last valid provider, account, model and effort used for this project. Open the New agent options when you want to change that setup or the number of agents, then leave the count at one for this first task. The result is the provider's real CLI in an interactive terminal pane. Its native commands, tools, settings, project instructions, MCP servers and permission prompts remain available.

A good first task is narrow, observable and explicit about verification. Adapt this prompt to a real issue in your project:

Inspect this repository and find the cause of the failing login form test.
Explain the cause briefly, make the smallest correct fix, and run the relevant tests.
Do not change unrelated files. Stop and tell me if the expected behavior is ambiguous.

For a read-only tour, ask the agent to map the project and choose Plan mode. For implementation work, review the behavior described in Permissions before changing the default mode.

Troubleshooting the first launch

• The provider is missing: confirm its official CLI is installed and available on your PATH, then reopen provider detection in KalCode.
• The account is signed out: reconnect it from Providers, then Accounts. Signing in from a separate terminal may use a different profile from the one KalCode manages.
• The agent will not edit: check whether it started in Plan, which is read-only, and read the provider's own prompt for any native approval it still requires.
• A command fails: read the terminal output, check or install the project dependencies the task requires, and honor any limit reported by the provider.

Once one agent works end to end, continue with Claude Code and Codex together or the parallel coding agents guide. Compare workflow features separately on Pricing.