Stars
Forks
Watchers
Developer links
Mikka
Instead of babysitting three coding agents in three terminal windows, you describe the work once and let Mikka run the team: its Coordinator bot plans the job, dispatches runs to Claude Code, Codex, or Cursor on your connected machines, and only interrupts you when a decision is actually yours. Every piece of work lives in a thread with its own conversation, so dispatched runs appear as cards that report progress, ask questions, and flag blocks while you watch, reply, or stop them from the web, desktop, or phone. Unclear requests come back as choice cards before anything runs, and finished work moves through review and verification runs, back to a fix run when a check fails, then to acceptance where the pull request merges as you. Runs use leases and checkpoints, so a machine that drops mid-task hands the work to another connected computer with the same repository. You can create your own bots beside the Coordinator, each with its own chat, memory, and threads, and answers can arrive as charts, tables, stat cards, and task chips with sources cited. Daemons connect over SSH or from the desktop app, other agents drive Mikka through MCP, and Telegram or Slack messages reach the Coordinator too. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
Benefits
- One Coordinator For Every Agent
- A built-in Coordinator bot triages requests, dispatches runs to Claude Code, Codex, and Cursor across your machines, and decides the next step when a run ends or blocks.
- You Approve, Agents Execute
- Unclear requests return as questions or choice cards before dispatch, workers surface blocks in their thread, and acceptance merges the pull request under your own GitHub account.
- Runs Survive Dropped Machines
- Leases and checkpoints let a run whose computer disconnects resume on another connected machine with the same repository, instead of losing the work and starting over.
- Your Keys, Your Infrastructure
- The self-hosted Docker server runs on your PostgreSQL with your own model credentials and OAuth clients, with billing disabled and no Mikka account required at all.
Features
- Threads With Live Run Cards
- Each run gets a named thread whose card follows progress in chat, with replies, questions, blocks, and stop controls on web, desktop, and mobile.
- Custom Bots Beside The Coordinator
- Create bots with their own name, avatar, chat, memory, and threads, all dispatching on the same loop as the Coordinator.
- Cloud Desktops, Take Over Anytime
- Every bot has a cloud desktop you can watch, take over when a run needs hands, and hand back afterwards.
- MCP, Telegram, Slack Access
- Other agents operate Mikka through MCP, and Telegram or Slack messages reach the Coordinator, so work starts where your team talks.
- Structured Answers With Citations
- Bots reply with charts, tables, stat cards, and question cards, and cite the tasks, runs, and pages behind each answer.