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
- 500
- planned
- 5,027
- shipped
- Plans, Approvals and Runs open on the whole project — a PROJECT tab gated by each room's view-any key, a MINE tab only for people who act, and view-only keys for plans and runs split from authoringRoles & 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) In 3D / Immersive, search matches on the roadmap canvas get no highlight: the style's panel shadow replaces the card's `ring-2`
- (motir-gateway) CodeQL email-injection #15/#16 — a validator-approved quoted address containing ";" becomes two malformed recipients, and the reset email writes the address unescaped into HTML
- (motir-core) `sdkSseGetSettled.test.ts` asserts ONE rate-limit row counting 3 with no window headroom — its 1.5 s-per-call hold straddles the 60 s mcp:call grid ~7% of runs and reds unrelated PRs
- The decision-confirmation read still computes the nearest epic (a walk-up plus a permissions and statuses read) that no client renders since the overturned band lost its epic entrance
- (motir-core) Two MCP transport tests still drive /api/mcp through a private UNTRACKED routeFetch — MOTIR-6324's migration missed them, and the in-flight probe fails unrelated PRs
- (motir-core) A plan that CHANGES the target itself is invisible from the level the surface now arrives on — the anchor is the level, and a level is not framed
- (motir-core) `workItemEmbeddingRanking.test.ts`'s at-scale cases each re-seed 1,500 vector rows inside the 15 s default timeout — they run 13–20 s on CI, and a timeout's leftover INSERT deadlocks the next test's reset
- (motir-core) `accountErasureSweepService`'s header says the `Ci*Usage` meters survive erasure — they cascade with the sole-member workspaces the same sweep deletes
- (motir-core) Opening a GENERATING named session may flash the roadmap before the live pane: the loading skeleton ends when the pending-proposal read returns nothing, and the pane swaps in only on the poll's first read
- (motir-core · design) Deleting an organization, drawn — the live Delete row and its confirmation (consequences, the organization's name, a password step-up), the Owner's scheduled card with Cancel deletion, the closing banner every member sees, and Transfer while closingRoles & 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 · docs+test) Correct AMENDMENT 16 D3/D8 and AMENDMENT 21 §6 to the SHIPPED rule — parking a card out of In Review CLOSES its awaiting gate — and make planHoldMovers.test.ts assert it
- (motir-core · decision) DECISION — how an organization is deleted: Owner + step-up + the typed name, a 30-day closing window, a read-only closing org, erasure through the shared workspace delete, an anonymised tombstone holding only the seven-year billing record, and every member toldRoles & 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) Dead code left by the one-level-builder change: seven `planChangeDiff` helpers and the `planningWorkspace.conversation.diff.*` copy keys have no production caller
- (motir-core) An automation rule whose transition meets a plan-held card records a FAILURE and counts toward auto-disable — AMENDMENT 21 §5(b) says a background mover records a no-op
- Production errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- PUBLISH Motir's Sentry integration — submit the publication request so a customer's own Sentry organisation can install it, and see it through Sentry's reviewProduction errors become planned work — a monitor connects, its issues arrive as bugs in a container the project chooses, and fixing one closes it back
- (motir-core · test) E2E + acceptance video — an Owner transfers the org, the new Admin creates and removes a workspace, a Member sees no org controls, and the Owner edits in a workspace they never joinedRoles & 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) The org-roles integration gate — the changed surface topped up to the 90% floor, the capability matrix driven through every route against the real database, and the one-Owner invariant racedRoles & 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) The account-deletion block tells the sole Owner to TRANSFER ownership and links straight to that flow, instead of asking them to give someone else the owner roleRoles & 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