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
- 要望
- 4
- 賛成票
- 375
- 計画済み
- 4,116
- リリース済み
- `transactionStall.test.ts` "reports an EXHAUSTED pool" flakes: the maxWait-rejected transaction's discarded BEGIN outlives the test and trips the in-flight probe
- (motir-core · design) The Instances page — where it is reached from, the empty state, the create dialog with its profile picker, the instance rows in every lifecycle state with machine time and credits, Wake, Delete with its confirmation, and every refusal in wordsYour own agent instances — host Claude Code, Codex or any sandbox agent in Motir's cloud on your own credential, see them on one page, work with one beside it, and let idle ones hibernate
- (motir-core) The Visitor view's shared page bodies don't know they are on a Visitor path — their links, pagers and load-more actions assume the member route and the active project, and a referer+cookie proxy redirect is the only rescue
- (motir-core) A server render failure lands on Motir's own error page — `app/(authed)/error.tsx`, `app/error.tsx` and `app/global-error.tsx` built to the drawn design, each reporting the caught error to Sentry with its digest, in `en` and `zh`
- (motir-core) A server render failure crashes the tab — no error boundary catches a throw in `app/(authed)/layout.tsx` or `app/layout.tsx`, so Next's `onUncaughtError` fires (seen on `/workbench` as a digest-only Server Components error)
- Mint the instance lane's fleet-organisation Fly token and set motir-core's three FLY_INSTANCES_* secrets — read each back from Fly before the story's pull request opensYour own agent instances — host Claude Code, Codex or any sandbox agent in Motir's cloud on your own credential, see them on one page, work with one beside it, and let idle ones hibernate
- Decision — a user agent instance end to end: the persistent machine and volume on the orchestrator port, hibernate and wake, the idle window and sizes, the instance record and its states, the per-interval charge, the fleet ceiling, the permission, and which sandbox profiles may be offered under each vendor's termsYour own agent instances — host Claude Code, Codex or any sandbox agent in Motir's cloud on your own credential, see them on one page, work with one beside it, and let idle ones hibernate
- Error: aborted
- (motir-marketing) `/docs/skills` gains the `motir-fix` usage section, the install commands move to its release tag, and the page E2E covers the new sectionMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-meta) Pin the `motir-skills` release that carries `motir-fix` — bump `PUBLIC_SKILLS`, add the skill to its list, and prove `install.sh` and the drift guard passMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (deploy) Release `motir-skills` with `motir-fix` — bump `plugin.json`, tag the next minor, publish the GitHub release, then install it from the tag as a consumer wouldMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- `motir-fix` ships — the next `motir-skills` release carries it, motir-meta pins that release, and /docs/skills documents itMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-core · design) The app's SERVER-ERROR page, drawn — a page that failed inside the shell, the whole signed-in shell failing, and the root failing: what the reader is told, Retry and the way out, in light and dark
- (motir-core) A plain workspace member can REPLACE the workspace's GitLab credential — `completeOAuthCallback` checks no role, and the upsert overwrites the existing connection with the member's own GitLab account and token
- (motir-core) Design — `/ready` grouped: runnable-container rows that expand to their ready leaves, standalone leaf rows, and a separate Bugs list (`ready--lanes.mock.html` delta)
- (motir-skills) The two-mode `motir-fix` skill — runbook mode routes to `prompts/fix.md`; standalone mode condenses the claim, the checkout on the pull requests' own branches, liveness, the CI-fix loop, the acceptance re-run and the closeMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-meta) The REPAIR protocol — `prompts/fix.md`: claim one card's repair, check out its pull requests' own branches, keep the repair alive, fix by `run.md`'s CI-went-red rule, re-record a sent-back acceptance, close with the outcome, reportMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (verification) The three repair tools are LIVE on app.motir.co — `tools/list` names them, and a claim → touch → close round trip works on a scratch card, with `taken` refused across MCP and CLIMotir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- Repair a red card from your own agent — confirm the repair tools live, then the repair protocol in the runbook and the two-mode `motir-fix` skill on `motir-skills` `main`Motir skills anyone can install — run, repair a red card, log bugs, fix the Bugs folder and be guided through manual work from the coding agent you already use
- (motir-marketing) CI on `main` has been red on every push since 2026-09-03 — the deploy's smoke check reads `motir-marketing.fly.dev`, which the host router sends to its 404 room, although the release itself succeeds