Skip to main content
You need an account or API key for your organization’s MKA1 gateway. The desktop package includes the coding runtime; you do not need to install the CLI or build the application from source. Before downloading, check whether your organization requires its own distribution. Use that package if it does; otherwise, use the public downloads below. You will also need network access to the gateway and the account or API key authorized for it. The model list depends on that access. The app bundles the agent runtime, but it does not install your project’s toolchain. For example, a JavaScript project may need Node.js and its dependencies before a test command can run. You can install the app and connect your account before setting up a project.

​
1. Download

Download the desktop installer for your operating system and processor. These links point to MKA1 Code 1.57.4. The public release manifest lists the published version and package checksums. On macOS, open About This Mac to check whether your computer has an Apple chip or an Intel processor. On Windows, these downloads support x64. On Linux, choose the ARM64 package for an ARM processor or x64 for an x86-64 processor. The package must match the computer where the desktop app will run.

​
Organization distributions

If your organization provides its own branded distribution or requires a specific release, use its packages:
  1. Open Apps in the MKA1 console and sign in. If your organization uses its own console address, open that console and select Apps at the bottom of the sidebar.
  2. Select your organization. Its distribution may use a different product name and logo.
  3. On the application’s download card, use Platform to select your operating system and processor.
  4. Choose Download beside Desktop app. For the other interfaces, choose the VS Code extension or CLI package.
If the required organization distribution is missing or unavailable for your platform, ask your administrator for its installer and gateway access.

​
2. Install

  1. Open the downloaded .dmg file.
  2. Drag the application into Applications and wait for the copy to finish.
  3. Eject the disk image, then open the installed application from Applications. Run the installed copy rather than the copy inside the disk image.
  4. Continue with Connect your account below.
If your operating system blocks the installer or application, contact your administrator for your organization’s installation procedure.

​
3. Connect your account

Sign-in opens in your browser. The code displayed by the app identifies the authorization request you need to confirm:
  1. Start sign-in. The app displays an authorization code and opens your browser.
  2. In the browser, sign in with your organization’s account. Check that the browser and app display the same code before approving access. You can copy the code or reopen the authorization page from the app while it waits.
  3. Return to the app when authorization completes. Check the model picker for the models available through your gateway.
If your organization supplies an API key, open Settings → Access, select API key, enter the key, and choose Use API key. The app validates it before activating it. Features that require account identity, including project memory, still require account sign-in.

Choose account sign-in or an API key in Settings → Access.

​
Choose a model

Open the model picker and select a model available through your gateway. For a text-only project question, start with a model your organization recommends for coding. If you will attach screenshots, choose one that accepts images. An empty picker is a connection or catalog issue to resolve before starting a task; it does not mean that the local project is empty. If sign-in returns you to the app but no models appear, check the gateway connection below. If authorization expired before completion, request a new code and repeat sign-in. See Usage and troubleshooting for the corresponding recovery steps.

​
Check the connection

In Settings → Connection, use the gateway URL supplied by your administrator. With an active credential, choose Test connection to check access and the available models. Testing does not save your changes; choose Save to apply them. Changing the server origin removes the active credential, so authenticate again after saving. You can also choose your language and theme in Settings. In local sessions, the agent and project tools run on your computer. In remote sessions, they run in the selected environment. Prompts, relevant file contents, and tool results are sent to your configured MKA1 gateway as context for model requests.

​
Verify the installation

After sign-in, confirm that the model picker lists models from your gateway. Then open a local project in Code and send a request you can check, such as:
Read README.md and explain what this project does. Do not change files.
If the project has no README.md, name another text file it contains. Confirm that a response arrives and inspect any file-read result in the timeline. To run project commands, install the project’s usual dependencies and build or test tools. Git is required for branches, worktrees, and commits. For remote sessions, these tools must be installed in the selected environment. Continue with Quickstart.