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
- solicitudes
- 0
- votos
- 373
- planificados
- 4054
- publicados
- 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
- MotirAiUnavailableError: motir-ai is unavailable: fetch failed
- (motir-core) Story E2E — two members edit a page, History lists both versions with their authors, the older one opens beside the current page, Restore makes it current as "restored from v1", a viewer sees no Restore; record the acceptance videoPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) Story VITEST gate — the coverage floor over the version modules, coalescing, the cap and restore on real Postgres, two authors' concurrent saves, `page_version` RLS, and the history routes' refusalsPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) RESTORE from the history panel — the confirm, the restore call, the open editor reloaded to the restored content, each refusal shown, held while edits are unsaved, and absent for a viewerPages — 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 HISTORY PANEL on `/pages/[pageId]` — the History entry, the versions list with load-more, and a version shown read-only beside the current page, with its loading, error and pruned-source statesPages — 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 page HISTORY ROUTES — list versions, read one version, and restore one, with every history 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) `pagesService` history — list a page's versions (keyset paged, newest first, authors batched), read one version, and restore a version under `page:edit` in one locked 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) `pageVersionRepository` and the `PageStore` adapter's VERSION methods — latest, insert, update, find, count and delete-oldest over `page_version` in the open transaction, mapped to the package's version rowsPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core) VERSIONS in `@motir/pages` — the per-author 10-minute coalescing policy and the 100 cap in `savePageUpdate` and `createPage`, the `PageStore` version methods, and the `restorePageVersion` procedurePages — 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 `page_version` TABLE — migration with the snapshot columns, unique page + number, cotenancy trigger, RLS, a backfilled version 1 for every existing page, and the Prisma modelPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- A page's history — versions saved as you write, who changed what, and restore to any versionPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- Run hosted: a double-click can refuse the second press as "not ready" because its own first press claimed the card
- (motir-ai) Code-graph size — unblock motir-core's index, stream hydration, explain the growth, and decide how the shared read path is split between tenants