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
- 需求
- 4
- 贊同
- 497
- 已規劃
- 4,958
- 已發布
- tests/reapOnReadResume.test.ts race test fails when the reap commits in the same millisecond the lease expires (strict greater-than on ms-truncated times)
- Planning bug (both planners): the corpus tells a planning session that whatever the settled requirement does not cover is a WHAT gap to stop on. A planning session may EXTEND the settled WHAT (edge cases, a more detailed workflow, side effects) and propose it in the plan; its only limit is not planning against it, and only an unbuildable or ambiguous WHAT goes back to the conversation
- (motir-core) Design: the per-repo convention cards on /code collapse — one card expanded at a time
- Write Motir's own repository rules into each repository's convention on /code — motir-core and motir-ai rules that only CLAUDE.md carries today
- Planning bug (both planners): a lay carries the parent's acceptance criteria without checking that its children meet each one or that shipped code allows it, and a contradiction with shipped code never reaches THE MARK STEP. MOTIR-7566 kept "another project → unavailable", which `resolveWorkItemRefSummaries` contradicts and no leaf builds
- `motir continue` refuses a run held by a design gate that was answered "changes requested", though that is a decided gate whose reason the run should read and act on
- The plan overlay says "That didn't go through" when its run stream drops on a network error (screen locked, laptop asleep), though the run goes on and succeeds
- Verify on the live tenant that the typed sections interface is served and enforced once the story's release is deployed
- A plan proposal's body link to a `planItem:` id that is not on the plan is accepted at every door and ships as dead text on the approved card
- (motir-core) /code errors for a project member (not admin) — the Health reads' `ai:configure` refusal is an uncaught PermissionDeniedError; members should see the whole page, Health included, read-only
- Design — the work-item EMBED CARD in a page (delta mock): the live card with key, title, type, status and assignee in edit and read, its archived and unavailable states, the picker's Embed-as-card choice, the toolbar entry, and the chip↔card convert affordancesPages and work items link BOTH ways — mention or embed a work item in a page, and see on every work item the pages that mention it
- Planning bug (both planners): the requirement's uncorrected recommendations are a prose string, so `answer_recommendation` numbers them by guessing at the prose. A `;`-separated list counts as one, every verdict on 2–5 is refused, and the briefing shows all of them unchecked. Make the recommendations and their verdicts structured data
- Design — the "code can't be searched" banner in the planning overlay (delta mock): which target repository, why, a link to the Codebase page, and resume
- A page version previewed in page history renders every mentioned work item as "Unavailable" — the version view is handed no summaries, and its read resolves none
- The load-test report sends a `fly auth token` to Fly's Prometheus as `Bearer` by default, which Fly refuses with 401, so every Fly CPU/memory/proxy line reads unmeasured unless LOADTEST_FLY_PROM_TOKEN_SCHEME=FlyV1 is set
- (motir-ai) A refused public calculator request (400) carries no Cache-Control: no-store
- Planning bug (both planners): the read-back rule covers behaviour claims only in steps and acceptance criteria, and the code-fact rule accepts a code-graph hit, so a test card's expected result can state what the code does without the code being read
- The same agent stays on its pull request until CI is green — a run in the person's own agent fixes a red PR by resuming its own session, and a red PR whose run has ended can be handed back to that agent with "Fix in my agent", for every agent profile
- Copy — the Fix in my agent words: the door and every state it can be in, the refusal when a fix is already running, the notice when the session could not be resumed and a fresh agent started instead, and the auto-fix setting's label
- Translate — ja, ko, de, fr, es, it, nl, pl and pt twins for every key this story's surfaces render: the nineteen Fix in my agent words from the copy card, including the auto-fix setting's label and help, recorded in each locale's sources file, so the nine interfaces stop rendering the English seed