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
- 요청
- 0
- 추천
- 369
- 계획됨
- 4,052
- 출시됨
- motir.co adopts the warm-touch default palette — re-pin `@motir/design-system` from 0.6.0 to the release that carries it, and prove the site renders it (motir-marketing)
- A Combobox menu inside `Modal.Body` is clipped by the body's scroll edge — only the first few options show (e.g. Add a model planning may use)
- Release `@motir/design-system` carrying the warm-touch Motir palette — merge the Version Packages PR, let the tag lane publish, and pull the published version from npm
- (motir-meta) Pin `.claude/skills/PUBLIC_SKILLS` to the release that carries the run-reporting `motir-run`, reinstall the doors, and `install.sh --check` reads cleanRun provenance — every run of a card records who ran it, on which model and for how long, however it was started
- (motir-skills · deploy) Release `motir-skills` with the run-reporting `motir-run` — the next minor tag and GitHub release, the plugin manifest's version bumped, then the skill installed from that tag as a consumer would and read backRun provenance — every run of a card records who ran it, on which model and for how long, however it was started
- Story E2E + acceptance video — the default Motir palette with its warm touches, light and dark, identity roles unchanged (motir-core)
- Story integration gate (motir-core) — coverage floor, seams and guards over the warm-touch palette change
- Apply the approved warm touches to the `motir` palette — light + dark tokens in `theme.css`, the separation / contrast suites over the new values, and `docs/palettes/motir.md` (motir-core)
- The default Motir palette gains a few warm-orange touches — Epic/Design chips, progress and tints warm up while the ink button, blue links/focus and ink logo stay
- Planning surface opens INSIDE a target that has no children — a childless story, task or bug lands on an empty level instead of beside the item
- A repo being re-audited says "started 2 weeks ago" — the in-progress row shows the PREVIOUS audit's time as when the new audit started
- motir-gateway's Fly image says it was built from `main`'s newest commit when it wasn't — on a `workflow_run` deploy, `GH_SHA` records the branch tip while the build checks out the commit CI tested
- Every card merged to motir-gateway fails CI on `main` and its deploy is skipped — `commit_lint` rejects the `MOTIR-<n> type(scope): …` squash-merge titles the card runs produce
- Two code-graph reads of the same cold graph at once: one waits and succeeds, the other fails `hydrate_failed` after 33 s — inside MOTIR-7619's 3-minute warming wait — and the convention job drops the cause from its error
- Motir inside Claude — a connector you sign into with your Motir account, one Claude Code plugin, and both listed in Claude's directories
- (motir-ai) graphRouting e2e "a recorded pointer's notice reaches the repository's two replicas only" sometimes gets 200 instead of 202 from a replica's refresh notice
- To fix is keyed per work item, not per run — one dead or red parent run shows up as a row on the parent and on every leg card
- The first read of a large code graph a graph-service machine doesn't hold fails — the download runs inside a 10-second request, so motir-core's audit says "not measured" until a retry finds the cache warmA dedicated code-graph service serves every tenant's graph reads, so any number of planning sessions read current code and the planning machines hold no graphs
- Adding a planning model asks for a typed model id — the dialog should offer every model the gateway serves that can plan (chat, planning-rated) and is not yet listed
- NotPlatformStaffError: The acting principal has no platform standing