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
- 500
- planned
- 5,029
- shipped
- The reflow breaks inline parentheticals — `(a)` and `(b)` are cross-references in this corpus, not list openers
- (motir-core) The PR lane runs the whole Playwright matrix on diffs a browser cannot reach — one `app` boolean gates six jobs, and 25% of recent pull requests paid ~62 runner-minutes for a lane with no signal in it
- CI Vitest flake, again: `truncateAuthTables` deadlocks (`40P01`) in `projectScopedDispatchRepo.test.ts`'s beforeEach on shard 8 and ejects an unrelated PR from the merge queue
- (motir-core) `acceptance-freeze-seam`'s publish-vs-approval race is FLAKY on CI — the approval rejects, and the spec asserts only `.status`, so the reason is never recorded
- The internal plan-proposal route answers 500 instead of a typed 4xx for a viewer's job token (PermissionDeniedError) and for a correction naming two repo fields (ConflictingTargetRepoInputError)
- (motir-meta) No step retires MIRROR.md's IN-FLIGHT rows when their motir-ai twin merges, so every twin-first change turns motir-meta `main` red
- (motir-meta) `main` is RED — motir-ai fe908d9 (MOTIR-6193) landed the twin of five IN-FLIGHT MIRROR.md rows and nobody retired them, so every open pull request inherits a red `guards complete`
- Four motir-ai coverage lanes are not in ci.yml, and two of them are already red on main
- (motir-core) The DIFFICULTY editor overflows the item page's 18rem rail — the four-segment control measures 316px against 258px of card, so High is clipped at the panel edge
- (motir-core · design) The DIFFICULTY editor at FOUR segments — a delta drawing the Segmented that fits the item page's 288px rail and the quick view's 300px one, at every shipped control-spacing token
- A gate's Request-changes note is unreadable by any agent — every door onto `ApprovalGate.noteMd` is session-authed, while MOTIR-6068 seeds a re-plan from it
- The corpus never names `update_plan`, so a planning pass cannot revise a plan's brief — and `plan-procedure.md` already instructs a close that writes the `summary` it has no door for
- A decision run is never told WHICH `docs/decisions/*.md` to write, how much of it, or that the file is what the reviewer READS — three rules missing from `run.md` 5b, two of them from the dispatch prompt too
- A decision card must never be planned MANUAL — `type-decision.md` binds the planner-recorded decision to `executor: human`, and MOTIR-6157 was laid that way
- (motir-core) The sandbox image ships no Python, so `motir sweep planning bugs` and `motir fix planning bug` cannot run their loop driver
- (motir-core) Sandbox coding agents cannot update themselves in a long-running container — install them into a prefix the runtime user owns, so an update needs no rebuild
- sandboxDigestTable tests hardcode `0.4.0` as the release being recorded, so every sandbox digest PR after 0.4.0 fails the CLI package lane
- (motir-core + motir-marketing) The sandbox guide's update step says "Dev Containers: Rebuild Container" without saying it only appears once the window is attached — attach via Open Folder in Container first
- 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…
- Published CLI rejects every additive server field — generated response validators enforce `additionalProperties: false`, so `motir link` fails since `difficulty` shipped