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
- 5
- richieste
- 4
- voti
- 375
- pianificate
- 4131
- rilasciate
- 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
- docs/mcp.md lists a work item's difficulty as `low | medium | high` — `trivial` (the fourth level) is missing on get_work_item, create_work_item and update_work_item
- TypeError: Invalid state: Controller is already closed
- (motir-meta) run.md's vitest guard `pgrep -af 'node.*vitest'` matches every sibling shell that runs the same guard, so "wait until empty" loops across sessions hold each other forever with no vitest running
- PrismaClientKnownRequestError:
- PrismaClientKnownRequestError: Transaction API error: A commit cannot be executed on an expired transaction. The timeout for this transaction was 5000 ms, however 19058 ms passed since the start of t…
- (motir-meta) `MIRROR.map.py --order` is red on `main` at 16 pairs against ORDER_PIN 15 — `phase-author.md` renders "Three sweeps" before "THE SURGICAL TOOLS", the twin composes them the other way round
- (motir-core + motir-marketing) The sandbox guide's VS Code route still goes stale and still loses the sign-in — MOTIR-4970 made only `docker run` disposable, and the page tells a Mac user the container can never sign in to Claude Code
- (motir-core) A `modify` peek's foot line says "only the description and the explanation" whatever the plan changed — a renamed card with a new body reads as if its explanation changed and its title did not
- (motir-core) `filter-builder-matrix.test.ts` goes red whenever the matrix runs across 00:00 UTC — rows seeded "today", relative-date cells queried "tomorrow"
- (motir-core) Can likely-ordering-violation reach an EVIDENCE-phrased post-deploy criterion? — measure it, and the answer may be no
- (motir-core) The item page's activity feed prints raw keys for Work type, Executor and Target repo — "changed the executor" — because the row's field-name map never lists them
- v1 plan-approval answers 500 for a plan with no proposals — PLAN_HAS_NO_PROPOSALS is missing from the v1 domain error map
- (motir-core) A scoped `motir run <story>` never holds a DESIGN child's dependents for its gate, and reads decision holds only once — a gate approved mid-drain releases nothing until the scope is re-run