Motir builds itself
How Motir builds Motir.
It sounds like a chicken-and-egg problem. It isn't. Motir started as a folder of prompts, and every feature it shipped became a tool for building the next one.
Where it started
We vibe coded. The project fell apart.
Vibe coding made the code fast. But the further we got, the more of the project we lost — because a project is not only code.
- A bug found, never trackedSpotted in the middle of a session, forgotten by the end of it.
- Too much at onceFive features in flight, and no way to tell which one to start next.
- Tests that weren't thereMissing, or not up to the standard the rest of the code needed.
- Decisions lost in a chatWhy something was built that way ended when the coding session did.
What we needed
Jira and Linear track work. We needed more.
We plugged our process into the project tools we knew. They held the tasks, but not the thing we were missing.
- 01A plan before the codeAn agent should start from a plan a person approved, not from a prompt.Motir AI Planner
- 02Ready, or blocked by whatSee which work can start now, and which waits — on exactly which other work.
- 03Someone running the whole projectA project manager that oversees everything and puts it together, without being asked.Motir Project Manager
So we built it.
The bootstrap
Every feature becomes the tool for the next.
Motir didn't wait to be finished before it was used. Each feature it shipped replaced the scaffolding it was built with.
- Day 0motir-metaAn internal project: a set of prompts, a task list and a store of mistakes. It prompted a model to build Motir's first features.Prompts and a task file
- ThenWork itemsWith work items shipped, Motir asked itself what to build next, not an outside tool.Its own work items
- ThenThe MCP serverWith the MCP shipped, those lookups became MCP calls, and status kept itself in sync.Its own MCP server
- ThenAI planningWith planning shipped, Motir planned its next features with its own planner.Its own planner
- NowAgents and approvalsAgents build Motir's work items; a person approves every plan and every merge.All of it
Build a featureUse itBuild the next one with it
Under the hood
The workflow that builds Motir is the one you get.
AI planning, the plan gate, agent runs, the merge gate, repair and the learning loop: every Motir project runs through the same workflow, this one included.
Still building
It hasn't stopped.
Motir is still adding features to itself, in public. These numbers are live from Motir's own project.
- 7,059
- shipped
- 572
- planned
- 6
- feature requests
- 4
- upvotes
Shipped lately
- MOTIR-11984Workbench: the "Waiting on you" count reads 0 while the tab lists a "Review to run" row — a review waiting to be started is not counted
- MOTIR-11983To approve: pressing a "Review to run" row leaves the Workbench for the item page instead of opening the approval overlay, where "Continue without the review" is
- MOTIR-11982To approve: a "Review to run" row's `motir review <KEY>` chip is wider than the DETAILS column, and its copy button lands on the WAITED text
- MOTIR-12013Design the tenant hosting accounts block on Fleet status: per-account quota rows with applied value, target, raise and the below-target flag
- MOTIR-11895Read the scip-dart and scip-php images back from the sandbox's indexer image repository
- MOTIR-11770(motir-infra) Read the deployed public SCIP upload listener back — its host forwards only the two upload paths to the codegraph-v2 API, answers 404 elsewhere, rate-limits per source, and the internal load balancer stays private
Build yours the same way.
Start with an idea. Motir plans it, builds it and keeps the whole project together.