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
- 503
- planned
- 4,952
- shipped
- (motir-core) The page TREE ROUTES — the level read, create with a parent, and the move route, with every tree refusal mapped to its HTTP statusPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) A FOLDER holds PAGES too — `deleteFolder` moves its pages up, and the folder level / contents counts and the delete dialog count pagesPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) `pagesService` tree — create under a parent, `movePage` in one transaction, the `/pages` tree level (folders then pages, keyset paged) and the page's trail for its breadcrumbPages — 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 PLACEMENT in `pageRepository` and the `PageStore` adapter — per-parent sibling locks and positions, the subtree read and ancestor rewrite, folder lookup, and the keyset level read of a parent's pagesPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) MOVE and PLACE in `@motir/pages` — create under a page or folder, the `movePage` procedure with cycle, depth and cross-project refusals, and the `PageStore` placement portPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- Pages in the project tree — a `/pages` tree of folders and pages, sub-pages, filing into the shared folders, moving and reordering, and the page's own sidebar tree and breadcrumbPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- PrismaClientKnownRequestError:
- PrismaClientKnownRequestError:
- PrismaClientKnownRequestError:
- PrismaClientKnownRequestError: Transaction API error: A commit cannot be executed on an expired transaction. The timeout for this transaction was 5000 ms, however 5108 ms passed since the start of th…
- PrismaClientKnownRequestError:
- PrismaClientKnownRequestError: Transaction API error: Unable to start a transaction in the given time.
- PrismaClientKnownRequestError: Transaction API error: Unable to start a transaction in the given time.
- PrismaClientKnownRequestError: Transaction API error: Unable to start a transaction in the given time.
- PrismaClientKnownRequestError: Transaction API error: Unable to start a transaction in the given time.
- (motir-core) Remove the cause of the production Prisma transaction stalls that MOTIR-6701's telemetry names
- An exec into an agent machine is cut off at 30 seconds — `flyRequest` aborts every Machines-API call at ORCHESTRATOR_REQUEST_TIMEOUT_MS, so a clone that takes longer fails the boot however long its exec was allowed to runYour 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) E2E jobs specs' beforeEach TRUNCATE hangs 30 s behind the lane's job worker, and the timed-out TRUNCATE stays queued and stalls the worker ~100 s, so unrelated PRs get ejected from the merge queue
- (manual) Submit the Motir connector to Claude's connector directory — listing, reviewer test workspace, data handling and the policy acknowledgements, through to a listingMotir inside Claude — a connector you sign into with your Motir account, one Claude Code plugin, and both listed in Claude's directories
- An agent instance whose Fly stop call fails stays `hibernating` with its machine still running, and no sweep ever re-issues the stop