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
- 488
- planned
- 4,829
- shipped
- Design: connect one GitHub account to many orgs — account picker, repo picker (available / unavailable elsewhere / none left), connected list, disconnect confirmationOnboarding 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
- Planning bug: `phase-lay.md`'s reconcile-rules header narrates the operation axis's retirement — and correcting a PACK is a two-repo act, because its prose is mirrored against motir-ai's twin
- (motir-meta) The planner corpus a session is sent names ~200 MOTIR work items, and nothing stops a new one — strip them and guard the composed prompts
- Two concurrent Resumes on one failed planning session can refuse the loser with PLAN_NOT_RESUMABLE instead of RESUME_ALREADY_STARTED
- The approval-gate and approve-and-merge readers crash on a delivery whose pull request the card's organisation can no longer read — refuse the decision instead
- (motir-meta) `plan.py` leaves an invalid plan `generating` forever: no planning session is handed the verdict to fix, and the plan is never closed with the reason
- Guide me through cannot read the project's code, so it tells the person to paste it and copies steps and SQL it cannot check — MOTIR-8129's query uses a table and columns that do not exist
- The internal plan-proposals route drops `summary` on a revision's final append, so a revised plan closes through `markPlanned` without the briefing the revision sent
- File the wave band as an EU figurative mark at EUIPO (canovol B.V., classes 9 + 42, wave-band.svg @ 91a9f3b2) and record the application number, filing date and sha
- (motir-core) A freshly deployed app machine takes traffic before it has loaded its routes or opened DB connections — its first requests fail with P2028 maxWait
- (motir-ai) The closing re-open scopes what it may fix to cards this run proposed, so committed cross-level edges and out-of-plan findings on not-done cards close the plan INVALID instead of being fixed
- IndexDispatchFailedError: Indexing moooon-B-V/nextjs-prisma-vercel-starter into project cmv3wr9xn00mrhxshj3j51xgl failed (admission_deferred): index admission was refused for 60 attempts (ai_plan_req…
- Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance…
- TypeError: Cannot read properties of null (reading 'checkRuns')
- 8.3.8 Trademark clearance search for the Motir brand mark (classes 9 + 42)
- The hosted plan revision never classifies and cannot search the rule corpus: `revisionClassifyAllowed` and `planningRuleSearchAllowed` are dropped by `assemblePlannerInputs`, so `classify_revision` and `search_planning_rules` are never offered and the classify-first gate never fires
- TypeError: Cannot read properties of null (reading 'owner')
- Guide me through overlay: the chat pane is cut off at the right edge and its divider cannot be dragged wider
- A guide turn whose message is a pasted code block fails with "structured response was not valid JSON" and the person's message is left unanswered
- PrismaClientKnownRequestError: Transaction API error: Unable to start a transaction in the given time.