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
- 贊同
- 535
- 已規劃
- 4,982
- 已發布
- Public follow confirmation and digest use the language recorded on the followMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Organisation and agents senders use each member's language with localized dates: data export ready, ownership transfer, organisation deletion set, agents deletion noticeMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Notification senders use each recipient's language: mention, watcher comment, watcher transition, filter subscription, failed automation ruleMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Account and sign-in senders use the recipient's language: password reset, email change, two-factor code, workspace inviteMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Record the follower's page language on email-only public follows (PublicFollow column, migration, written at follow time)Motir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- Email language plumbing: recipient-language resolver (an address with an account but no saved language resolves English, never the recorded language), locale carried through the email.send payload to the template, lang on the HTML rootMotir in eleven languages — app.motir.co and motir.co in en·zh·ja·ko·de·fr·es·it·nl·pl·pt, per-language font sets, and work content in an org content language with per-user translation
- A hosted or agent-instance run's agent cannot call any Motir MCP tool its dispatch prompt names — record_run_discrepancy on a build-through, and the STOP branch's comment, Planning transition, append_plan_turn and submit_plan_session
- Design: the tab resumed after being hidden — several changes land at once (check design-notes § 26 first)motir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- Planning bug (both planners): a requirement that narrows WHO may do an act ("only the STOP branch files a planning bug") is laid without enumerating every site that does the act today, so the log-bug.md route that misfiled MOTIR-8646 got no card
- motir.co's subscribe form does not send the page language, so an email-only follow records the browser's language instead of the page's
- Motir AI chat panel: an assistant message's long lines and code spans run past the panel instead of wrapping, and the log scrolls sideways
- Guide me through shows each step twice — the model restates the step and the code appends the same step block after it
- Read back from Fly's managed Prometheus that production's app machines are scraped on the [metrics] port, and that the per-route and per-tool p95 wait/hold queries return data — name the machines and release that answeredmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- Decision — the generated first-project name is never rendered on onboarding, and its settled shape is a lowercase hyphenated adjective-noun-number placeholderOnboarding 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
- A run that stops on an unbuildable card reaches Motir's planning-bug home only from the runbook and a tenant's own machine — hosted runs, agent-instance runs, an agent with no Motir MCP, and Motir's own CLI dispatch never file one
- Planning bug (both planners): a re-lay gap with a BODY half is reported "raised and closed" when only its structural half was answered, and a gap raised after the re-lay about stale sibling bodies is handed back and never reaches the briefing, so the person approves stale cards believing they were reconciled
- Planning bug (both planners): a committed card re-titled in a level's RE-LAY is never re-authored. MOTIR-8644's authoring list is drained only before the re-lay, and the re-lay is told never to re-draft a body, so the card keeps its stale body under the new title
- A plan's change to an existing card cannot set its to-do list — `todos` is refused on a `modify` patch, so a re-plan can neither give a person's card steps nor replace a stale list
- A run builds through a plan that is wrong only about the HOW — it records each discrepancy on the run and the card, and stops, re-plans and may file a planning bug only when the WHAT breaks
- (motir-meta) `log-bug.md`, `_shared.md` and `core.md` gate 15 stop routing a defect into `Bugs / Planning bugs` — a planning bug comes only from a run's STOP (THE RUN-FOUND CONDITION, `unchanged`) or `plan-procedure.md` act 5; every bug `motir log bug` files takes the two placement branches, whatever it is about