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
- 597
- planned
- 5,376
- shipped
- (motir-ai) The planner PROPOSES into a folder — `folder:<id>` accepted by `propose_node`, `author` and `place_node`, validated against the grounded folder set, and passed through the registry, author sessions and revise passFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) A plan READS its folder placements — the review model's folder trail, `get_plan` grouping under the folder path, and `folderPath` on the `/api/v1` plan proposalFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) Plan proposals may NAME a folder — `folder:<id>` accepted as an `add`'s `parentRef`, a `modify`'s `patch.parentRef` and `update_plan_proposal`'s, validated at append on the MCP and internal doorsFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) MCP work-item tools PLACE into folders — `create_work_item` and `move_to_parent` take a `folderId`, and `get_work_item` declares `folderId` + `folderPath` instead of leaking the id through a spreadFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) `/api/v1` work items report and take a FOLDER — `folderId` + `folderPath` on the detail read, `folderId` on create and PATCH refused beside `parentKey`, and `motir show` printing the folderFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-ai) The planner READS folders — `folderId` and the folder set on its tree reads and grounding, `docs/contract.md` §6, the skeleton tool rendering a filed item's path, and `contextualScope` reading placement off skeleton rowsFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) The planner's TREE READ carries folders — `PlanTreeSkeletonItem.folderId` and a `folders` list on `readPlanTree`, served by MCP `skeleton` and the internal `plan-tree` / `skeleton` / `get-subtree` routesFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) MCP FOLDER TOOLS — `list_folders`, `create_folder`, `update_folder`, `delete_folder`: permissions, registry, tool-doc catalogue, `docs/mcp.md`, generated schemas, and folder refusals as typed tool errorsFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) The `/api/v1` FOLDERS resource — list a level (keyset-paged), create, rename / move / reorder, delete with contents moved up; every folder refusal mapped to its status and code; OpenAPI operations and the contract versionFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) PLACEMENT in the service — `createWorkItem` takes a `folderId`, a re-parent through `updateWorkItem` clears the folder instead of tripping the XOR CHECK, and one placement rule that lets a filed subtask be a rootFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- Agents and integrations file into folders — `/api/v1` and MCP folder doors, folders on `skeleton`, and plans that propose into a folder with the reviewer seeing where each card landsFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- (motir-core) Turning the acceptance video on still fails to repaint ~1 press in 16 WITH the server half in place — and the trace excludes the MOTIR-5118 race
- (platform, manual) Raise the `motir-integration` GitHub App to `contents: write` and re-consent its installations — merging a pull request needs it, and the granted set is read back from the App's own APIApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core · test) `issue-detail-flow.spec.ts`'s link-management tests navigate right after the OPTIMISTIC row assertion, before the link write commits — :622 ejected PR #2869 from the merge queue
- (motir-core) Design — a proposal FILED into a folder on the plan review: the canvas breadcrumb's folder crumbs, the arrival level for a folder-placed card, a move into or out of a folder under Show changes, and the folder deleted before approveFolders — a project's tree can be tidied into nestable folders that hold any work item and carry no workflow of their own
- 8.99 (motir-core) The design-asset address guard reads a prose glob `/x/*` as the page `/x` — it rules on the family's PARENT, so a family with child pages and no parent page is falsely reported dead
- 2200.43 (motir-core) A storage-cap refusal on the item page's Attachments panel reaches the user as a 500 and then as "Upload failed — please try again" — `/api/work-items/[id]/attachments` maps no `EntitlementExceededError`
- (motir-core) The gate read's `canDecide` skips the kind's permission FLOOR — a project viewer who is the assignee is drawn Approve / Request changes that the decide door then refuses
- (motir-core) Playwright acceptance E2E + VIDEO — click a To-approve row, read the design at full size, approve it there, and come back to the tab with the row settled and the count one lower (en + zh)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- (motir-core) The story's VITEST GATE — the coverage floor over the overlay, its host and its route, the route → overlay → frame seam, and the guards a percentage cannot see (ONE close seam, TOTAL over `ApprovalGateKind`, no second approve control)Approval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join