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
- 需求
- 0
- 赞同
- 375
- 已规划
- 4,100
- 已发布
- (motir-core) The relay carries a chat channel — the owner-only ticket names the channel, the relay dials `/v1/chat` with the same token, chat frames bump activity like terminal frames, the chat channel refuses in words when the agent's image has no chat server, open and close recorded, no frame loggedYour 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 · CLI) The in-agent server serves `/v1/chat` — the relay token verified as for the terminal, the transcript event protocol, the adapter contract and the supported-profile answer, one running turn per agent with Stop, the session list and resume delegated to the adapter, the sign-in gate, no prompt, reply or tool output logged, released by a changesetYour 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
- Chat with your agent in the panel — a session transcript with its tool calls and a prompt box, for every profile whose CLI streams a headless session, beside the terminalYour 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
- (ops) Run `motir-codegraph` on two always-on machines — `fly scale count 2`, read back from `fly machine list`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
- Roles & 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
- (motir-core · verification) VERIFY the retired access level is GONE from production — no `project."accessLevel"` column or `project_access_level` 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
- (motir-core · test) E2E + acceptance video — open /code for a repository refused for size, read the size, the limit and the suggestion, then see the row return to normal after a successful indexA 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 · 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