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
- 557
- planned
- 5,451
- shipped
- 30 (motir-core) `motir doctor` PASSES the agent-credential check on a DIRECTORY — `claude` (and `codex`, `kimi`) probe `~/.claude`-style folders, so "credential present" is true on any machine that ever launched the agent, and always true in the sandbox because the folder IS the mount
- Planning bug: MOTIR-4652 was laid `ready: true` with an acceptance criterion only a SIBLING FOUR HOPS DOWN ITS OWN CHAIN can satisfy — and its "not in scope" section names that sibling
- Planning bug: the corpus asserts the default workflow has NO direct `in_progress → done` edge — MOTIR-1625 ADDED it, with a backfill, and the false claim is what makes a container's unguarded close read as impossible
- Planning bug: a re-plan enumerated a table's RLS arms from two MIGRATION FILES instead of `pg_policy`, missed one, and wrote the resulting false absence into a plan, two cards, a bug and a shipped global lesson
- Planning bug: a bug card's FIX DIRECTION named one refused read and stopped — the next read in the same bound transaction was never checked, and the card sealed with an accepted over-gate advisory it had named a split for
- (motir-marketing) Publish the disposable-container recipe on `motir.co/docs/sandbox` — transcribe the literal the motir-core sibling settled, and drop the keep-the-container paragraphs it makes wrong
- (motir-core) The CLI REPORTS its version on a dedicated field and the server warns below a floor — the only signal that reaches a sandbox already running in the wild
- (motir-core) `motir` tells you when it is OUTDATED and offers to upgrade — with the sandbox's root-owned global prefix handled rather than assumed writable
- (motir-core) Make the sandbox container DISPOSABLE in the in-app guide — the credential moves to a named volume, and `--rm` + `--pull=always` replace `--name` and `docker start`
- (motir-core) Three `packages/cli` specs fail on macOS and pass on Linux CI — they compare an unresolved `join(root, …)` against a realpath'd cwd, so `/var` vs `/private/var` reddens every local run
- (motir-core + motir-marketing) A returning reader's sandbox silently runs a STALE CLI — `motir login` was `Unknown command` on a six-week-old container, because the guide has to tell readers to keep the container the credential is trapped in
- (motir-core · design) A class the TREE styles and Tailwind cannot name is unmeasured — 165 occurrences of 21 across 28 mocks, and `ic` is declared in 60 assets while 3 carry it bare
- (motir-marketing) Bring the PUBLISHED devcontainer recipe on `/docs/sandbox` back into agreement with the one the image ships — the `postStartCommand` line and the paragraph that stops calling the two routes interchangeable
- (motir-core) Make the NINE in-repo devcontainer recipes and the guide's published recipe RUN the agent-config setup — `postStartCommand`, and the sentence that says why the VS Code route needs it
- (motir-core) Make the sandbox image's agent-config setup RE-RUNNABLE and reachable from a shell that never went through the entrypoint — `motir-sandbox-agent-config` + the login-shell hook
- 29 (motir-core + motir-marketing) The sandbox's devcontainer route BYPASSES the image entrypoint — `overrideCommand: true` replaces `motir-sandbox-entrypoint`, so `CLAUDE_CONFIG_DIR` is never exported and the agent falls back to the read-only `~/.claude` it can never sign in to
- 2200.8 (motir-core) A proposal's ROW pin `targetRepositoryRef` has NO reader anywhere in motir-core — the one pin that lifts the repeated-role ceiling is persisted and dropped at approve
- (motir-core) SCHEMA — the `ApprovalGate` table, its migration, its RLS under the `motir_app` non-bypass role, and the repository leafApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join
- 27 (motir-core) A card the plan RE-PARENTS onto a level arrives with NO dependency edges — the review canvas seeds its arrows from the level's CURRENT children, so a committed edge appears only after approve
- (motir-core) AMEND the approval-gate ADR — the two WORKFLOWS, the `approved` status, the third kind, relationship-or-admin authority, and the pin re-keyed onto the subjectApproval gates — every decision that holds work up happens IN Motir, behind ONE approve language new kinds join