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
- Anfragen
- 0
- Stimmen
- 369
- geplant
- 4.052
- ausgeliefert
- (motir-core · test) Story test gate — coverage floor over the boot driver, the step record, the boot read and stream, and the panel's read-out; create → driver → steps → running against the real database and the fake fleet; a failure on each step; the driver, the sweep and the run launcher racing one boot with one winner; a stream resumed from its cursor; the owner-only refusalYour 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) Story E2E — an agent with a device-grant token creates a page from markdown over `/api/mcp`, a person opens it at `/pages/<id>` and sees the same content, edits it, the agent's stale update is refused by name and a current one landsPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) My agents — Create closes on the server's answer and opens the new agent's panel, and the panel reads out the boot live (waiting, in progress, done, failed, skipped, one row per repository) while starting and waking, then collapses to a summary once running; the booting list row; en and zh; built to the approved deltaYour 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) Story VITEST gate — the coverage floor over the markdown write, the service doors and the three tools; the editor-written page read back as markdown; a markdown write racing an editor save on real Postgres; cross-project and missing-key refusals; the CLI grant reaching all three toolsPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) `page:view` and `page:edit` join `CLI_TOKEN_GRANT` — argued at the constant, in catalog order, shown on the device approval screen, with the device-flow wire string, the grant guards and `HOSTED_RUN_TOKEN_GRANT`'s subset test brought along, and `page:delete` kept outPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The boot read and its live stream — GET …/instances/[id]/boot and …/instances/[id]/boot/stream (server-sent events with a step cursor, a heartbeat and a done frame), owner-only, on the dispatch-run stream's conventionYour 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 `create_page` and `update_page` MCP tools — a markdown body under `page:edit`, `create_page` filed under a parent page, a folder or the root, `update_page` refused by name on a stale revision, each page refusal mapped to a tool error, in every home a tool hasPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The `get_page` MCP tool — a page's markdown, placement, revision and latest version by project key and page id under `page:view`, registered in every home a tool has: registry, permission map, annotations, payload, published catalogue and generated schemas, `docs/mcp.md`, and the tests keyed by tool namePages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The boot driver — an `agent-instance/boot` job advances one boot attempt the moment each step is possible, holding the attempt's lease, recording every step, cloning one repository per exec, and failing on the step it is on with its reasonYour 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) `pagesService` markdown doors — `getPageMarkdown` (`page:view`: title, placement, revision, latest version's number and author, body markdown), `savePageMarkdown` (`page:edit`, with the revision read) and a create that takes an initial markdown body and a parent, each in one transactionPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The MARKDOWN WRITE in `@motir/pages` — `savePageMarkdown` checks the revision the caller read under the page lock, turns the markdown into one Yjs update and saves it through the ordinary path, refusing a stale revision with `PAGE_REVISION_CONFLICT`Pages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) The boot-step record — one row per step of each boot attempt (step, repository, state, started and ended times, detail) with RLS in its migration, its repository, and the boot read's DTO and mapperYour 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 · orchestrator) describePersistent reports the machine's lifecycle events — launch, start and exit with its code and time — in the Fly and fake adapters, so a boot can name the step its machine is onYour 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
- Agents read and write a page over the MCP — `get_page` by id returns its markdown, `create_page` / `update_page` take a markdown body, and a dispatched agent's grant can use themPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- Watch your agent boot — Create closes at once and opens the new agent's panel, and the server drives the boot to running or failed while the panel reads out every step liveYour 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 · design) ARCHIVE, RESTORE and DELETE a page — Archive… on the tree row and the page, the archived-page banner, the Archived pages list in `/pages`, the permanent-delete confirm, the restored-elsewhere notice, and every refusal and role statePages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- A card at In Review with a red open pull request is missing from To fix: the repair predicate admits In Review only for a merge-queue exit, and nothing holds a card that reaches In Review already red
- (motir-core) Two concurrent wakes can leave the woken agent running with NO fleet slot — the losing wake releases the slot it reserved, which the winning wake was relying on via `already_held`
- (motir-core) MCP tool descriptions link their own API reference — clears the connector directory's "Reference the target API docs in the description" suggestion
- A cancel racing the CLI's close leaves an "ended (cancelled)" line on a run that ended succeeded