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
- 499
- planned
- 4,801
- shipped
- `motir auto` never records its legs: the idempotent re-open ignores the new card, so every per-card event 422s
- Enable pg_stat_statements on the production Neon database and read it back with the checked-in command — CREATE EXTENSION over the direct connection, once the story's merge has put the command on main (a staging branch cut from production afterwards inherits it)motir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- To resume keeps listing a card that has since reached In Review with its pull request open — resume should reconcile it, not stamp or re-run it
- (motir-ai · motir-core) A planning job that fails reading the project back from core loses its cause and the session says "the AI provider was unavailable"
- To resume keeps listing a parked scope run's old cards after a plan re-shapes its story: new children never appear and re-scoped ones are not flagged
- Planning failure: ai_job_failed in a entry_author session on MOTIR-8239 — gateway: tool "report_findings" arguments were not a JSON object
- Onboarding's GitHub connect says what will happen on GitHub before you leave, brings you back to the step you started from, and has explicit install-cancelled, no-repositories-selected and already-connected statesOnboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- The onboarding substrate reads an organisation's connected repositories, so a run let through by the organisation-tier exit gate is not grounded on "no repositories"Onboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- The connect step's exit gate — an organisation that already has connected repositories can leave the step, whichever of its workspaces connected themOnboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- Translate — the connect step's new copy and the owner-approval banner into the nine other app languages (ja, ko, de, fr, es, it, nl, pl, pt)Onboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- E2E — the onboarding GitHub connect round trip and every outcome state, in English and Chinese, with a paced acceptance videoOnboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- Integration — the setup callback's outcomes across both return surfaces, against the real datastoreOnboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- The connect step — pre-flight, one action per outcome state, and no control that does nothingOnboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- Translate — the connect step's new copy and the owner-approval banner into ChineseOnboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- Copy — the connect step's pre-flight, every outcome state and the owner-approval banner, in the message cataloguesOnboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- Service + route — the connect step's read: the organisation, its usable repositories, and whether an installation is boundOnboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- The App-install round trip — starts on the connect step, returns there with the run's context, and reports an owner-approval request honestlyOnboarding that matches motir.co — the Motir look and "vibe the project" voice, a GitHub connect that does not lose you, no waiting on the index, a generated first-project name, and import proven against real Jira, Linear and Plane
- The Workbench live stream keeps polling the database after the reader leaves
- A parent run over MCP never reports a manual child as skipped / needs_human, so no manual_work gate is raised and the card is missing from Waiting on you
- Usage & cost hides the Translation line when an organisation's only AI spend is translation (hasUsage ignores translation)