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
- 494
- planned
- 4,822
- shipped
- Planning bug (hosted): author sessions raise a gap for work they could shape with the surgical tools, and raise_gap accepts it without naming the undecided decision
- MonitorLinkNotYetVisibleError: The monitor link for work item cmv779k7l0r1ihnpxhl2j65na (connection cmv3kxq6z00k5hwsh69rqeybk) is not visible yet.
- The error monitor files the same issue again and again: a bug cancelled as a duplicate counts as completed, and a re-file whose link write times out leaves the issue pointing at the old bug, so every poll files another
- Planning bug: a plan whose author sessions failed still closes as planned, and its briefing never says which cards were left unwritten (hosted planner)
- A hosted revision's re-lay withdraws a proposal but leaves it in the pass's registry, so the author scheduler opens paid author sessions on proposals that no longer exist
- A hosted plan revision's lease lapses after 10 minutes without a plan write while the job is still running, so the plan reads Proposed with Approve live mid-rewrite
- Planning bug: the post-merge cut fires on the provenance phrase "read on `main`" and spawns a human deploy card that copies the whole source body
- Planning bug: the briefing prints the conversation's code-unverified recommendations as "not corrected" even after the lay read the code and planned the opposite (hosted planner)
- Planning bug: producer and consumer cards of one cross-repo seam are authored in parallel, so they specify contradictory wire contracts. A blocked_by added during authoring never re-orders or re-authors the consumer.
- Planning bug: a lay that names its committed target by id instead of key lays a level the walk never finds, so no card is authored and the plan still closes as planned
- Verification — the Motir App's configured permissions, as the connect step's pre-flight states 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
- Planning bug (plan.py): the brief session is never asked to check the conversation's recommendations against what later sessions found, so section 4 can repeat an overturned guess as "not corrected"
- A conversation plan's target leaves Planning 30 minutes after the session's last turn while its plan still waits for approval: the sweep spares only plan-held locks
- Planning bug (plan.py): a plan whose author sessions failed still closes as planned, and the briefing only mentions the failure if the brief model chooses to
- plan_inbox.story.test.py scenarios 10, 12, 13 and 14 race the pause gate and fail intermittently under CPU load
- Planning bug (plan.py): a gap the re-lay neither answers nor lists as unanswered is silently dropped. Its re-lay never answers each gap by name.
- Design — the connect step's pre-flight and every outcome state it can return inOnboarding 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
- (motir-ai) The planning-deploy e2e test fails by 1 ms: its 310 s hold wakes a millisecond early against Date.now(), and step 6 then fails behind it
- plan.py deadlocks after a paused change is answered: the resuming thread keeps the pause gate while its relay's author sessions wait at that gate
- Planning bug: a re-lay marks every gap it was handed "raised and closed" by whatever it added, so a gap nothing answered reads as done in the plan briefing