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
- 524
- planned
- 5,590
- shipped
- Onboarding's "Save & exit" returns to `/dashboard` under a comment calling it "the app's default authed landing" — a third stale home constant the MOTIR-3171 sweep did not enumerate
- (motir-core) `detect-stray-design-results.mjs` scans ZERO rows and exits 0 on the connection its own USAGE prescribes — RLS hides every row from `motir_app`, and an empty sweep is indistinguishable from a clean one
- (motir-core) `E2E_TEST_AI_JOBS=1` on its own installs NOTHING — the instrumentation gate omits its own flag
- The E2E boundary mocks trace the WHOLE project into the standalone build — one Turbopack warning, and it names whichever mock it reaches first
- (motir-core) The Motir AI callout stays OPEN while the orb is dragged and thrown — the panel rides across the viewport with it, then strands ~818px away mid-flight, because nothing in the gesture path touches the popover's `open` state
- `design-assets-uploader` test reaches REAL git — it fails on any branch whose HEAD is a merge commit
- (motir-core) A second `modify` for the same work item in one plan fails with a raw Prisma unique-constraint string, not a typed error
- (motir-core) A plan abandoned in `generating` can NEVER be decided — the sweep is empty-only, and a partial plan has no discard path
- MOTIR-3104's merge-parent guard CANNOT fire in the depth-1 clone it was written for — a shallow graft hides HEAD's parents, so the publisher falls through and puts another card's design onto whichever branch is open
- (motir-core) `planning-workspace.mock.html` paints the orb in three INVENTED hexes — it cannot follow a `data-palette` swap, and its first stop is 2.995:1
- (motir-core) A CANCELLED workflow run poisons a card's CI verdict for good — its rows merge by NAME with the re-run's, so an all-green PR reads `failing` and the card never leaves `implemented`
- (motir-core) The dragged orb is fought over by CSS — `hover:scale-105` MULTIPLIES the position because `scale` composes before `transform`, and `transition-transform` eases every physics frame, so the bounce lands ~480px from the wall
- (motir-core) The floating orb's glyph misses WCAG 1.4.11 in DARK — white on the gradient's lightest point measures 2.78:1 against a 3:1 bar
- (motir-core) `ai:view_plan` gates no view — one key holds AUTHOR and DECIDE, so a custom role granted "can see plans" can materialize a tree
- (motir-core) A titles-first plan cannot be CLOSED — `add_plan_items` demands at least one proposal, and the two-phase path has nothing left to append
- (motir-core) A `modify` proposal renders UN-PARENTED on the plan review surface, so an amendment to an existing card reads as a new card at the project root
- A design child that ships on the PARENT-RUN branch reaches no card — the publisher resolves its target from the BRANCH, which names the container, so the assets are declined and never re-addressed
- (motir-core) The signed-in shell scrolls the DOCUMENT as well as its own `<main>` — the body floor is `100vh` where the shell is `100dvh`, so a browser whose two viewports differ gets an empty band and a second scrollbar
- (motir-core) A DECIDED plan breaks the planning workspace — the rail keeps a LIVE Approve gate and never says what landed, and every accepted card is drawn TWICE on the canvas (holding `main` red since MOTIR-3154)
- The `claude` sandbox image stopped building at 00:53 UTC — `@anthropic-ai/claude-code@2.1.237` shipped WITHOUT its x64 platform packages, and an absent OPTIONAL dependency is not an error