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
- 501
- planned
- 4,774
- shipped
- Scale-out and scale-in against the Fly Machines API — create a machine with the same image, size and process group, and remove one by drain: stop it with SIGTERM, let in-flight reads finish inside the 60 s kill_timeout, destroy it only once it has left vms.motir-codegraph.internal, so a move never fails a readPlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- (motir-ai) The scaling decision engine — a signal past its threshold for its whole window adds, a brief spike adds nothing, one scale-out at a time, sustained low removes one, never below 2, and every decision is logged with signal, value, threshold, window and resulting countPlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- (motir-ai) Scaling settings read from config — per-signal thresholds, windows, sustained-low window, floor of 2 and an optional ceiling, as the decision's placeholders, with no hard-coded capPlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- (motir-ai) Each graph machine exposes its scale signals — memory use against budget, read p95 and the download backlog (the depth of the hydrate queue behind the 2-download limit)Planning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- (motir-ai) Fix the notice timeout at its own layer, with a regression test that fails before the fix — the notice stays fire-and-forget, replicas-only and never slows the pointer writePlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- (motir-ai) Trace the [graph-notify] refresh-notice timeouts of 2026-10-16 to a named cause — which leg ran past 2 s, with every ruled-out hypothesis recordedPlanning capacity follows demand — a conversation turn never waits behind a planning run, the planning machines and the graph service grow and shrink on their own, and a load-tested cost ceiling is the only fixed limit
- The fleet job inventory is re-measured only by hand, so any workflow edit in a private repo marks image coverage inventory_stale and blocks the Motir-CI-on-fleet switch until someone notices
- The sign-in probe that gates Send to my agent always reads a signed-in agent as signed out — its exec runs without the agent-config environment, so it stats ~/.claude and ~/.codex instead of where the sign-in livesYour 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
- The open agent's panel on My agents is cut off below the boot read-out — the tab strip shows but the terminal area under it is clipped
- An undecided plan is unreachable (no Approve or Decline) when a later plan in the same session is decided
- Fleet runners have no disk Docker can use: overlay is refused on the Machine's rootfs and the vfs fallback fills it, so every services: job dies with ENOSPC in its install step
- After the chat story MERGES — release the `motir` CLI that carries the chat server: merge the Version Packages pull request, see `cli-v*` publish the sandbox images, pull the Claude Code and Codex images by digest and see the chat server in them, and chat on a production agentYour 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
- The page MCP tools cannot change a page's title — create_page sets one, update_page and the rest cannot rename it
- After the run story MERGES — release the `motir` CLI that can run a card inside an agent: merge the Version Packages pull request, see `cli-v*` publish the sandbox images, pull the Claude Code and Codex images by digest and see `motir agent-terminal run` in each, and see a production agent created after it pin that digestYour 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
- Planning bug (plan.py): a session copies the 25-character plan id into its tool calls by hand and can mistype it, so every plan write is refused PLAN_NOT_FOUND, the card stays title-only and the retry repeats the same id
- (motir-marketing) Make the request-rendered allowlist a CI guard and the sitemap's site half static, with the project half emitted per host
- (motir-marketing) Build the four generated reference pages and robots.txt at deploy — force-static, artifacts fetched once per build, a failed fetch fails the build
- (motir-marketing) motir.co times out: the four generated reference pages, robots and sitemap still render in the serving process — build them at deploy, per the MOTIR-8838 decision
- After the terminal story MERGES — release the `motir` CLI that carries the terminal server: merge the Version Packages pull request, see `cli-v*` publish the sandbox images, pull the Claude Code and Codex images by digest, and open a production agent's terminalYour 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
- After the boot read-out story DEPLOYS — on production, create a real agent and watch its boot read out live to running with a terminal prompt, then hibernate and wake it and watch the clone rows read skippedYour 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