moooon
Motir
Vibe the project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.
- Vibe Project
- Open Source
- AI Agent
- AI Loop
- 6
- requests
- 4
- upvotes
- 410
- planned
- 4,717
- shipped
- Cover every remaining place a work content field is rendered, or record it as this story's named exception, with a guard that fails when a new one appears uncoveredMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- The list, tree, board, backlog, sprint, roadmap, ready and triage surfaces — titles in the reader's language with per-title loading, a per-surface Show original switch and one no-credit noticeMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Work item page and quick view — every field arrives in the reader's language on load, with the machine-translation marker, Show original, and an editor that always opens the originalMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Route — the batch title translation endpoint, with the target language taken from the reader's own request and never from the bodyMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Settings → Project — the Auto-translate work content control, its read-only state for a member without the permission, and the change read-backMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- The many-titles translation door — a bounded set of work items' titles translated in one request, kept per item, field, revision and language, refusing to spend when the project's switch is offMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- The reader's translation context — the project's switch, the reader's interface language, whether the organisation can pay, and each title's recorded language, resolved for every covered surfaceMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Route — read and flip a project's auto-translate switch, refusing a caller without project:administerMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Service — read and flip a project's auto-translate switch behind project:administer, recording every change in the same transaction as the writeMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Schema and migration — the project's auto-translate switch, off for every existing and every new project, and the trail of who changed it, from what, to what and whenMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Codex will not start in a hosted agent — the sandbox image ships no `ps` (procps), so Codex's app-server startup failsYour own agent instances — host Claude Code, Codex or any sandbox agent in Motir's cloud on your own credential, see them on one page, work with one beside it, and let idle ones hibernate
- (motir-core) 6 index container usage rows in 2026-10 never reached `destroyed` — 3 `destroying`, 2 `stopped`, 1 with no terminal state
- Planning bug (both planners): a production-verify child was laid inside story MOTIR-8787 whose merge it waits on; the rule is prose-only, so a recurring miss passes validation and approval
- The CLI's close racing a Cancel answers 500 in the merge queue, ejecting the PR (agentInstanceRunStoryGate)
- Each pool scales on headroom: a suspended machine wakes when free slots fall below the watermark, a machine is created when none is left to wake, idle machines suspend and long-idle ones retire, a wake that never answers is retried or replaced, and only real work keeps a machine awakePlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- (motir-ai) Extend the Fly stand-in for the headroom e2e — a create route that spawns a real process, records.creates, and updated_at on every listing rowPlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- (motir-ai) Story e2e on the planningPool.e2e harness: wake before the queue grows, create once none is left, suspend then destroy down to the floor, other pool unaffectedPlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- (motir-ai) Integration test: headroom scaling seams — coverage floor over the story's changed surface, created machine eligible to poolSnapshot and inside runDeploy's retire set, per-pool isolationPlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- (motir-ai) Only work routes reset the idle clock — other requests count in flight but do not touch lastActivityAt; GET /health stays ignoredPlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- (motir-ai) Retire long-idle machines inside the existing sweep: one machine per pass, oldest-suspended first, never below the pool floor, never with a running job, retire mark or non-current releasePlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit