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
- 已發布
- Onboarding moves on while the code index builds — no wait-for-index stop, progress shown where it does not block, planning told the graph is still being built, and an indexing failure surfaced later without undoing onboardingOnboarding 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-core) Story E2E: connect, walk past index, indicator, Enter Motir while indexing, failed index and retry, in English and ChineseOnboarding 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-core) Story integration test gate: index exit, retry, and Enter Motir completing the run while the index and import keep runningOnboarding 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-core) Import step: Enter Motir as the primary action, a started import shown running in the background, and the rail without the questions step (en + zh)Onboarding 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-core) Onboarding-chrome indexing indicator with openable detail (index per repo + the work-item import), failed state with retry (en + zh)Onboarding 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-core) Enter Motir finishes migrate onboarding from the Import step while the index and any import keep running, and the run reports the project's latest importOnboarding 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-core) Retry a failed index from the onboarding run by reusing the existing index re-enqueueOnboarding 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-core) INDEX step exits once an index exists in any state, and the index-status read reports queued / indexing / done / failed per repoOnboarding 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-core) The org switcher cannot switch to an organization that has no workspace — the shell stays on the org that owns the pinned workspace cookie
- A dedicated code-graph service serves every tenant's graph reads, so any number of planning sessions read current code and the planning machines hold no graphs
- (verify) On production, the planning pool suspends when idle, resumes in about a second on a turn, scales out to a second machine under five concurrent sessions, and suspends again after a deployA dedicated code-graph service serves every tenant's graph reads, so any number of planning sessions read current code and the planning machines hold no graphs
- Planning bug (both planners): cards state what existing code DOES, logs or supports without reading it, and nothing checks the finished cards against the code or against each other — the same plan written by a cheap and by an advanced model carries the same wrong facts
- Provision staging — its own Fly app (`app` + `worker`, `app` machines the size production runs, read back with `fly machine list --json`), a Neon branch copied from production with its own pooled and direct URLs, secrets pointing every side effect at a sink, and a load-generator machine in `iad`, each read back from the platformmotir-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
- (motir-core) "New workspace" creates the workspace in the org the stale `motir.org` cookie names, not the org the shell shows; the public-project submit hint names that org too
- (motir-core) The org settings pages (usage, billing, members, security) read the stale `motir.org` cookie, so after a workspace switch they show another organization than the shell names
- A realistic sample project, committed as one reusable vendor-neutral fixture — epics, stories, subtasks, statuses, assignees, labels, comments, links and sprints / cycles — for the import proofs to loadOnboarding 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
- Story test gate: the check passes on the committed fixture, fails naming the item on a broken parent id and passes after undoOnboarding 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
- Build the CI check that validates the fixture: kind-parent matrix, depth, dangling ids, person emails, iteration membership, naming the offending itemOnboarding 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
- Write the per-vendor expected-result file: each fact marked must-arrive or known-not-read by the shipped connectorOnboarding 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
- Write the per-vendor translation table: Jira, Linear and Plane representation of every fixture concept, incl. kind without a native type and iterationsOnboarding 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