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
- 추천
- 380
- 계획됨
- 4,067
- 출시됨
- (motir-gateway) The catalog refresh REMOVES the hand price of a model its provider no longer lists — the refresh PR deletes that id from `provider_direct_prices.json` and names it in the body, instead of the price staying on the books with no check reading it
- (motir-core) The hosted smoke test "a parent, continued" flakes under load: the run's close is sometimes never recorded
- (motir-gateway) The SOURCED provider-direct prices move into a data file the refresh can rewrite — each one's prompt, completion and provenance leave `model.go` / `price_provenance.go` for `relay/billing/ratio/provider_direct_prices.json`, and every charged price stays the same
- (verification) The continue tools are LIVE on app.motir.co — `tools/list` names them, `dispatch_prompt` takes `continueFrom`, and a claim → touch → prompt → close round trip works on a scratch card whose run was killed
- Remove the hand-kept leftovers of RETIRED `deepseek-v4-flash`: its price rows in the gateway and the "fast" planner option in motir-core. The catalog refresh has already stopped routing it
- An agent can add and tick a card's to-do step over the MCP but never delete or edit one — `workItemTodosService.deleteTodo` / `updateTodo` ship with a UI door and no MCP tool
- (motir-meta) `install.sh` and `SKILLS_DRIFT.check.py` read the public skills from the release's `plugins/motir/skills/` via a `skills_dir=` pin key, so motir-meta can pin `v0.4.4`
- (motir-skills) The public `motir-fix` skill's acceptance re-run knows who publishes — standalone mode stands down where the repository's lane carries the uploader, `SYNC.json` re-hashes the merged `fix.md`, and the README line matches
- (motir-meta) `prompts/fix.md`'s acceptance re-run knows who publishes — where the card's repository lane carries the uploader, the re-record is CI's green re-run and the repair makes no MCP publish
- (motir-core · test) The story's integration gate — the restored uploader driven through the real publish routes over a locally minted OIDC token into a real evidence row, a closed story skipped, a CI and an MCP publish of one commit collapsing to one receipt, and the coverage floor over the changed surface
- (starter) The starter's acceptance lane publishes again — vendor motir-core's restored uploader at a stamped ref, wire it PR-only over keyless OIDC with no token secret, invert the MOTIR-4097 guard block, and rewrite `docs/acceptance-video.md`
- (motir-core) The dispatched agent and `motir fix`'s closing turn stand down where the repository's lane publishes — `ACCEPTANCE_PUBLISH_STEPS` and `renderAcceptanceRecordPrompt` check the checkout for the uploader before publishing over MCP, and `CLAUDE.md`, `playwright.acceptance.config.ts` and `docs/mcp.md` say who publishes now
- (motir-core) The acceptance lane publishes again — restore the uploader script, its composite action and its tests from `76add02b1b^`, brought up to today's server (`STORY_CLOSED` skip, the PR's card key as `producedByKey`), wired PR-only over keyless OIDC, the MOTIR-4096 guard block inverted, and the ADR amended
- CI publishes the acceptance receipt again in the repositories Motir builds — motir-core's and the starter's acceptance lanes upload the recording from a green PR run over keyless OIDC, and the agent stands down wherever its repository's lane publishes
- SyntaxError: Unexpected end of JSON input
- (ops) Run the planning pool on 5 machines — `fly scale count 5 -a motir-ai`, read back from `fly machine list`A 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
- TypeError: Cannot read properties of undefined (reading 'icon')
- (motir-core · design) The PAGES section — a Pages entry in the project sidebar, the `/pages` index with New page, and the page at its own address: saved / saving / offline / too-large, read-only, loading and not-foundPages — a project's documents: write a page, keep it in the project tree beside the work it describes, and keep its history
- (motir-core · test) Story integration gate — the continue tools through the real MCP transport: parity with the REST claim, `taken` across MCP and REST, every refusal, liveness past the lapse, idempotent close, and `dispatch_prompt`'s CONTINUE prompt equal to the REST route's
- (motir-core) The MCP door onto the CONTINUE CLAIM — `claim_work_item_continue`, `touch_work_item_continue` and `close_work_item_continue` over `workItemContinueService` and the dispatch-run heartbeat and close, and `dispatch_prompt` takes `continueFrom`