Miko brings self-hosted coding agents into team conversations
Miko connects a team's existing conversations and issue trackers to a coding agent running in its own workspace. The official product site describes a self-hosted system that takes tasks from services such as Slack, Linear, GitHub and GitLab, then brings results back into the same workflow.
Assign work where the discussion happens
You can assign a Linear issue or mention Miko in a connected conversation. The site describes supported coding agents including Claude Code, Codex and Cursor, with additional agent options also listed.
Miko coordinates the task and repository context while the selected coding agent performs the investigation and implementation. That separation helps explain what you are choosing: a way to connect and manage agent work, alongside the coding agent you already use.
Keep tasks separate and continue by reply
Each task gets a separate Git worktree. This lets a bug fix, documentation change and feature investigation proceed without placing all edits in one checkout.
Follow-up replies can update an existing task. The publisher describes retaining the conversation context when someone adds an edge case or clarifies the request. This is useful for teams that refine requirements while reviewing an agent's progress, rather than trying to predict every detail in an opening prompt.
Miko returns pull requests for human review. Its examples include running configured checks and summarizing changes, but those examples are product demonstrations, not a verification of a specific repository's test coverage.
Plan the host and review process
The site also describes scheduled tasks and a local task board. Because Miko is self-hosted, the machine running it and the connected accounts remain part of the operational setup.
Start with a small issue in a repository you can safely review. Check the diff, reported tests and requested service access before expanding its role. Keep the existing team's decision about merging and releasing code explicit.