Mirako

Mirako

A DX studio for the agentic era.

We build the tooling that sits around coding agents — the backlog they read, the docs they can trust, the surface they act through.

Currently issues, self-hosted tracking with an MCP
Focus Context, surfaces, handoff
Contact hi@mirako.computer

Agents can write the code now. Everything around the code is still missing.

They start every job blind to the backlog, read docs that stopped being true two refactors ago, and act through whatever surface happened to be lying around. So does the next person on the team — we watched a bug cross three people on WhatsApp and arrive with less detail than it started with. That gap is the brief.

What we work on

Three problems. Everything in the shop is aimed at one of them.

Context

What it knows before it starts

A readable backlog, and docs that match the code. An agent that starts blind writes the wrong thing confidently, and you find out in review.

Surfaces

What it acts through

Issues, links and state that a person and an agent can both read. One surface, no translation layer bolted to the side of it.

Handoff

Where a person takes it back

One click into your harness with the issue already loaded. Work should move between hands without being explained twice.

What’s in the shop

Six things, labelled how they actually are. One is moving, three have stopped, and one isn’t even ours — which is more useful to say than to hide.

In dev
issues

Self-hosted issue tracking, deployed at your own domain, with an MCP so an agent can read the backlog it’s working from. A step up from a GitHub tab, a step down from Jira.

A real morning, with somewhere to put it See the whole thing
09:04
The CEO opens PL‑7 from the WhatsApp thread: bad scraper result, screenshot, product URL.
09:04
The agent reads it over /mcp — the thread, the URL, two open issues on that same store.
09:31
Pushes pl-7-rank-fallback, opens !41, posts the fix back to WhatsApp.

Open source and self-hosted. A hosted instance, run by us for teams who would rather not manage another box, is planned and is what will fund the open one.

in development · first team is PriceLantern, four people
Paused
toka

A harness that hands the model one JavaScript REPL instead of twenty narrow tools, and lets it write its own. Next: finish it, then benchmark against ordinary tool-call agents and publish the numbers.

noxire-dev/toka
Stopped
lumiko

Generates docs from a codebase with Claude, including a context.json written for agents rather than people. Unfinished, and published in that state on purpose.

mirako-studio/lumiko
Stopped
kodo

A web GUI for driving coding agents, built on T3 Code. They shipped the same idea faster, so we stopped. One idea would restart it: first-class pi and toka integration.

noxire-dev/kodo
Internal
hako

The shelf for tools that didn’t want their own domain. Holds yomu and the design system this site is built from. Publishing planned.

no repo yet
Side
tayf

A Turkish news bias analyser across 144 outlets, built with a friend. Nothing to do with coding agents — listed because it’s real and we’re building it.

side project, two of us

Where it’s going

issues is the one in active development: self-hosted tracking with an MCP, so the agent working your repo reads the same board you do.

Everything else in the shop feeds that idea. Each tool does one thing and stops. When one starts growing a plugin system, that’s usually a sign it should have been two.

Working on something near this?

Agent tooling, self-hosted things, or you just want to argue about what an MCP surface should look like. We answer.

hi@mirako.computer