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
- 5
- richieste
- 0
- voti
- 374
- pianificate
- 4101
- rilasciate
- (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
- (motir-core · design) The VERIFIED-BY-DOMAIN state — a delta on the consent screen, the sign-in hand-off and the Connected apps card: an app verified as its client-id host (Claude · claude.ai, Claude Code · claude.ai) beside the Unverified and Registered states, and the access path unchangedMotir inside Claude — a connector you sign into with your Motir account, one Claude Code plugin, and both listed in Claude's directories
- Claude's plugin directory still holds `motir` v0.4.1 over the repo's own test and CI scripts — ship the plugin from its own folder so dev tooling is not in the bundleMotir inside Claude — a connector you sign into with your Motir account, one Claude Code plugin, and both listed in Claude's directories
- (motir-core · verification) VERIFY the retired role storage is GONE from production — no legacy column, table or type in the catalog, no schema drift against the serving build, and no missing-column error in any of the three release windowsRoles & permissions, refined — org Owner · Admin · Member, ROLE on the workspace and ACCESS on the project, an automatic Visitor on public projects, and a UI that offers each role only what it can do
- Retrying a debug turn that already landed submits a second paid debug_bug job
- (motir-core) shared-store.test's DEGRADED-store case leaves a real rate_limit_counter INSERT running when a non-staged increment loses its 200 ms deadline — the in-flight probe reds unrelated PRs
- Claude's plugin directory holds `motir` v0.4.0: a policy hold on `$PWD`/`PIN` read as credentials, and no listing icon or privacyPolicyUrlMotir inside Claude — a connector you sign into with your Motir account, one Claude Code plugin, and both listed in Claude's directories
- The "code graph was refreshed" notice names a source-tree hash as if it were a git commit
- (motir-ai · test) E2E — recording a new pointer through motir-ai's real route makes the separately running graph service fetch it, and the next client read downloads nothingA 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 — a refreshed graph answers with no download, the old commit serves during the download, and reconcile recovers a lost notice, a crash and an unread 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) The control plane notifies every running graph machine after it records a new snapshot pointer — fire-and-forget, so a failed notice never fails the pointer writeA 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 graph service reconciles at boot and every 10 minutes — fetches stale recently read graphs, deletes unread and offboarded ones, and clears crash leftoversA 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 graph service's refresh endpoint — a signed notice of a new pointer prefetches a repository read in the last 7 days, and every read reports whether it downloadedA 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 graph cache downloads a new commit beside the old one and swaps after verifying it, and records each graph's commit and last read in an on-disk manifestA 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