Mikka

AI agent coordination across your computers and the cloud.

Mikka organizes work for Claude Code, Codex and supported Cursor runners, with bots that coordinate tasks and agents that execute them.

Open Mikka · Documentation · Quickstart

English · 简体中文

Describe a task to a bot. Mikka dispatches coding work to agents on your Mac, Linux machine, SSH server or an eligible cloud sandbox, then brings their progress, questions and results back into one place. Use it in the web, macOS or iOS app.

Get started

Mikka Cloud (early access). Open the app. If you need access, email mikka@aspectlylabs.com, then follow the Quickstart.

Self-hosted server. Mikka can run on your own Linux host with Docker and PostgreSQL. Follow the self-hosting guide to configure credentials, download the matching Compose file and start the server:

docker compose up -d --wait

The Compose deployment starts the Mikka server and PostgreSQL; it does not install a separate copy of the official UI. Connect an official client to your server. See Client and source availability before choosing self-hosting.

Already use Claude Code? Connect Mikka as an MCP server:

claude mcp add --transport http mikka https://app.aspectlylabs.com/mikka/api/mcp

This registers Mikka in Claude Code and uses browser-based OAuth sign-in. You need access to the Mikka server; the command does not install the Mikka daemon or run a coding task. See the MCP guide for other clients and tools.

What Mikka does

• Coordinates work. The built-in Coordinator and bots you create turn requests into tasks, clarify ambiguous instructions and dispatch work to coding agents.
• Runs where your work lives. Connect your own computers and SSH servers through the Mikka daemon, or use a configured cloud execution environment. Eligible parallel coding runs use isolated Git worktrees or task sandboxes.
• Keeps work reviewable. Follow task progress, answer agents' questions, inspect run results and review eligible pull requests through Factory's checks and acceptance flow.
• Provides cloud desktops. On configured Mikka Cloud accounts, bots can use a desktop you can watch, take over and hand back. Direct E2B access uses the owner's own key.
• Works with existing tools. Reach Mikka from Claude Code or Codex through MCP, or from Telegram and Slack. Connected-app actions respect the relevant permissions and approval policy.
• Bring your own subscriptions. Use your existing Claude or ChatGPT/Codex subscription with supported coding agents. Model API keys are also supported where applicable.
• Supports personal and team work. Tasks, bots and activity can be organized across personal and team workspaces, with access controls for connected resources.

Availability depends on deployment configuration, connected services and feature flags. Planned work is tracked in GitHub Issues, not represented here as shipped functionality.

How it works

1. Describe the work. A bot turns your request into a task and asks for clarification when needed.
2. Dispatch an agent. Mikka selects a configured execution location and starts the coding run.
3. Follow along. The agent reports progress or questions; you can respond when it needs input.
4. Review the result. Factory applies the checks required for the task, sends failed work back for fixes and presents eligible code changes for acceptance. An authorized acceptance can merge the PR using your connected GitHub account.

For definitions of bots, agents, tasks, threads and runs, see the glossary.

Client and source availability

Mikka has one official UI across its web, macOS and iOS clients. Those clients can connect to Mikka Cloud or a self-hosted server.

This public repository includes the server, daemon, native mobile source and much of the web UI code. Official web and desktop builds also use private UI components that are not distributed here. A build from the public source alone is therefore not the complete official web or desktop UI. A legacy built-in workspace UI remains available behind an opt-in flag, but is not a second supported product design.

Read UI source boundaries and self-hosting for what can be built, deployed and connected. Source implementation and production availability are verified separately under the acceptance policy.

Development

The repository uses Node.js 24.x and pnpm 10.34.3. To install dependencies and run the source checks in a prepared development environment:

pnpm install --frozen-lockfile
pnpm check

For a runnable local environment with an isolated PostgreSQL database, follow the cloud Linux bootstrap and development workflow. Do not commit credentials; the project uses Infisical for development secrets.

Core stack: React, Vite, Hono/Nitro, Vercel AI SDK and Workflow, PostgreSQL/Drizzle, Electron, Expo and the Mikka daemon. See the documentation index for architecture, integrations, CI, deployment and runtime details.

Documentation

• Quickstart — get started with the official app.
• Self-hosting — run your own server and connect clients.
• MCP integration — operate Mikka from other agents and tools.
• Documentation index — architecture, setup, security and operations.
• Contributing and AGENTS.md — contribution and coding-agent rules.

Open source and licensing

The public source is licensed under AGPL-3.0-only. Modified versions offered as network services are subject to the AGPL's source-availability obligations. Third-party components retain their own licenses; see the third-party notices.

Commercial licenses are available from Aspectly Labs at legal@aspectlylabs.com. Contributors retain copyright in their work and grant the additional licensing rights described in CONTRIBUTING.md.

Acknowledgements

Mikka's maintainer received six months of ChatGPT Pro access through the Codex for Open Source program. Mikka is independent and is not affiliated with or endorsed by OpenAI. The OpenAI name and logo are trademarks of OpenAI.