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
- 518
- planned
- 4,959
- shipped
- (motir-core · test) Integration — a size-refused run against a real database: not re-dispatched, recorded on the repository, rendered on the DTO, cleared by the next success, and coverage over the changed filesA 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
- (motir-core) The /code Repositories row says a repository's graph is too large — the DTO carries the refusal, and the row renders the size, the limit and the suggestion as the design draws them, in English and ChineseA 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
- (motir-ai · test) Integration — the size refusal end to end in motir-ai: the grant's boundary at and over the limit, the recorded failure surviving the container's report, the verdict read, and coverage over the changed filesA 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
- (motir-core) An index run refused for size is not re-dispatched — the settle reads the run's failure, records the refusal on the repository, and the next successful index clears itA 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
- (motir-core) A repository remembers that its last index was refused for size — the `GithubRepo` columns, their repository writes, and `fetchCodeGraphRunVerdict` reading the run's `failure`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
- (motir-ai) The upload grant refuses a graph over the supported maximum — 1 GiB by default, configurable, a 422 `graph_too_large` carrying `sizeBytes` and `capBytes` like the graph service's, and the refusal recorded on the runA 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
- (motir-ai) An index run's failure record keeps a size refusal — the `GRAPH_TOO_LARGE` class with the graph's bytes and the limit, never overwritten by the container's later `GRANT` report, and returned by `GET /v1/code-graph/run/verdict`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
- A repository whose graph exceeds the supported 1 GiB is refused at indexing, and its code-graph status says whyA 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
- (motir-ai · test) E2E — with the graph service running as its own process, a planning session pages through tools, the audits match their in-process results, and a stopped service yields the existing unavailable pathA 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
- (motir-ai · test) Integration gate — the consumers' coverage floor, the remote-result seams into each reader, and the no-graph-on-the-planning-app guardA 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
- (motir-ai · docs) `codegraph-production-topology.md` §1 and §3 point at the graph-service decision instead of describing the in-process read pathA 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
- (motir-ai) Delete the in-process read path from the planning app — the `hydratingGraphStore` singleton, offboarding's local evict, and a guard that only `src/graphService/` may open a graphA 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
- (motir-ai) `security_audit` takes file reachability from the service, walking every page — no `readSlice` of the whole graphA 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
- (motir-ai) `code_audit` and conventions measure from per-repository graph signals the service computes — no `readGraphSlice` in either jobA 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
- (motir-ai) Bug authoring and debugging ground through `RemoteGraphStore` — `codeGraphGrounding`'s default store, for `author_bug` and `debug_bug`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
- (motir-ai) The six planner graph tools read through `RemoteGraphStore` and page — "page 1 of N" in each result, and a `cursor` argument that returns the next pageA 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, audits, conventions and bug authoring read code only through the graph service, and the planning machines no longer hold graphsA 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
- A container never completes when one of its repositories shipped through a Done human card with no pull request: the repo-set gate holds it at In Review/Approved for ever
- The agent-instances coverage lane measures no My agents file: its `app/(authed)/…` glob matches nothing
- The `motir` plugin's listing has no terms of service — `plugin.json` sets no `termsOfServiceUrl`Motir inside Claude — a connector you sign into with your Motir account, one Claude Code plugin, and both listed in Claude's directories