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
- 499
- planned
- 4,801
- shipped
- Integration test of the retention pass against the real database: what survives, the watermark, dedup inside the window, batch bound and backlog drainmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- Record the new dedup horizon in the job-queue decision recordmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- Retention service and the daily system.job-queue-retention job reporting rows deleted per tablemotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- Retention repository methods: batched delete of old succeeded job_queue rows, their job_step rows and orphaned job_event rows, with window and batch constantsmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- Audit every job_queue reader and record each one's keep-rulemotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- A person reading a plan or an approval never sees the page refresh under them — every router.refresh() and whole-page re-render on the plan, approval and Workbench surfaces replaced by an in-place update of only what changedmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) The To approve and Planning tabs apply a nudge in place — their rows read from the one endpoint's approvals and planning windows into client state, merged by identity, no route refreshmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) Story E2E with acceptance video — a reader through a 50-write MCP burst on a generating plan, a planned plan, an approval and every Workbench tab: zero _rsc refetches, zero document loads, place preserved, Approve keeps the decided planmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) Story integration test gate — coverage floor, appliers driven from a fake signal source, rows/counts agreement, render-count and DOM-mutation assertionsmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) An architecture guard fails when router.refresh, useCoordinatedRefresh or window.location is reachable from the plan, approval and Workbench live-update pathsmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) The open approval reads the seam, never refreshes its page — subject-moved notice unchanged, port scroll, selection and half-typed refusal text survive every update, over /workbench and over an item pagemotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) Approve lands without a route refresh — the planning hosts reconcile the decided plan from the approve response and the review read, and the Workbench counts behind the overlay are current when it closesmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) A plan snapshot is MERGED into the screen by identity — unchanged snapshot changes nothing, a changed proposal re-renders alone, a withdrawn one disappears, in PlanDetail, usePlanGeneration and usePlanChangeConversationmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) The Workbench applies a nudge in place — rows and counts held as client state from the one endpoint, rows merged by identity, no route refresh, and nothing refreshed while an approval is open over itmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) ONE Workbench read — an endpoint returning the active tab's window and all five counts from a single server read, sharing the page's pairingmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) The live-signal SEAM — one source-agnostic 'something moved' input the Workbench, approval and plan appliers read, with the SSE nudge and the 2.5 s plan poll plugged in as today's sourcesmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) Confirm the refresh-under-an-open-approval cause — a spec that counts RSC refetches and document loads while an approval is open over /workbench and over an item page during a write burstmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- No correctness depends on one instance — every in-process state in motir-core's `app` (rate-limit buckets, caches, locks, dedup and the live-update hub) found, and either moved to shared state or shown safe per instance, proven by a two-instance test where a request and its follow-up land on different machinesmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) Scripted two-machine staging check — the limit and follow-up cases run against a base URL, each request pinned with `fly-force-instance-id`, output naming which machine served the first and second requestmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test
- (motir-core) Story integration gate against real Postgres — coverage floor over the Better-Auth storage, the memory-store guard and every moved row, and the guards that no module-scope state returns for themmotir-core's web tier scales horizontally under agent traffic — each added `app` instance adds throughput (~500 req/s per instance, toward ~10k active agents), connections stay bounded, no reader is refreshed, measured first and proven by a re-runnable load test