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
- 贊同
- 500
- 已規劃
- 5,029
- 已發布
- (motir-core · orchestrator) The persistent port moves a machine to a new image digest on the same volume — running or stopped, the mount and every other config field kept — and runs a liveness command inside a started machine, in the Fly and fake adaptersYour own agent instances — host Claude Code, Codex or any sandbox agent in Motir's cloud on your own credential, see them on one page, work with one beside it, and let idle ones hibernate
- (motir-core) The published-image catalog — the newest version and digest per offered profile read anonymously from GHCR and cached, an agent's own digest named by its version, and the agent DTO says Update available with the target version, or nothing on the newestYour own agent instances — host Claude Code, Codex or any sandbox agent in Motir's cloud on your own credential, see them on one page, work with one beside it, and let idle ones hibernate
- A debug turn loses its anchor chip and outcome line after a reload of the Motir AI rail
- An instance offers the newer sandbox image and moves to it on your say-so, keeping its home and sign-inYour own agent instances — host Claude Code, Codex or any sandbox agent in Motir's cloud on your own credential, see them on one page, work with one beside it, and let idle ones hibernate
- (verification · human) The connector proven live on app.motir.co — discovery and the 401 read back from production with the running release named, then a claude.ai custom connector signs in, approves one workspace and answers a readMotir inside Claude — a connector you sign into with your Motir account, one Claude Code plugin, and both listed in Claude's directories
- Superseded code-graph snapshots are never pruned from object storage since the index fleet took over publishing
- (motir-ai) motir-ai reports errors and operator alerts to Sentry — `@sentry/node` in both apps, a `raiseOperatorAlert` helper, and the DSN from configA 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 — the graph service as its own process, called by `RemoteGraphStore` over HTTP, answers exactly what the in-process store answersA 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 graph service's routes against a fixture graph: credential refusals, current-pointer answers, paging, computations and budgetsA 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 API reference — `docs/graph-service-api.md`: every endpoint, the credential, paging and the error codesA 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) Ship the graph service as its own Fly app — `fly.codegraph.toml`, its start command, and a CI deploy step on merge to `main`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) `RemoteGraphStore` — the `CodeGraphStore` client over the graph API: signs each call, follows pages, and maps failures to `CodeGraphUnavailableError`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 graph service computes whole-graph results itself — the graph half of the code metrics and file reachability, so no caller ever pulls a 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) The graph service app — `/v1/graph/*` routes for the six reads, paged, behind the credential, answering from the repository's current pointerA 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 budgets — a per-graph cap, the memory LRU and RSS line from config, a disk LRU over closed files, and at most 2 concurrent downloadsA 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-read credential — motir-ai signs a 60-second token for one organisation and repository, and a verifier refuses anything elseA 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
- The graph service answers a tenant's code-graph reads over a signed, paged HTTP API from the repository's current commitA 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 P2028's pool tags describe whichever pool registered last — the Next server builds one PrismaClient and pg Pool per Turbopack runtime, so a route handler's timeout can report a page runtime's idle pool
- The CONTINUE prompt tells the next agent a hosted or agent run that stalled or hit its 12-hour backstop "stopped reporting"
- (ops) Create the `motir-codegraph` Fly app — one performance-1x 4 GB machine, its secrets, the shared signing secret on both apps, and a CI deploy tokenA 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