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
- 534
- planned
- 4,982
- shipped
- (motir-core · decision) Running a card in your agent — the detached launch through the agent's terminal server, the run's credentials kept off the agent's home, each profile's unattended agent command and the profiles that cannot run, the sign-in and image-capability probes, `origin: instance` and the agent on the run record, one running run per agent, and what hibernate, delete, a lost machine and Cancel do to a live runYour 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 · test) E2E + paced acceptance video — open a hibernated agent from the list and watch it wake into a live terminal, type and resize, lose and regain the connection, sign in through a stubbed vendor CLI and see the status turn, close the panel and let it hibernate, reopen still signed in, and another member refusedYour 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 · test) Story test gate — coverage floor over the terminal server, machine process, relay and panel; the relay → real terminal server seam, owner-only refusal against the real database, a live terminal holding the agent awake, sign-in status from a real credential file, and a guard that no stream byte reaches a logYour 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 agent panel on My agents — a row opens the agent in the right half with the list still usable and the address naming it, opening wakes it, the header's live state and sign-in status, Hibernate and Delete, and the terminal tab on xterm with resize and reconnect, built to the approved deltaYour 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 terminal relay — the owner-only ticket, opening a hibernated agent wakes it, bytes carried both ways and never stored or logged, activity bumped while a terminal is live, open and close recorded, and the sign-in status read through itYour 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) An agent's machine runs the terminal server as its main process and the relay can reach it — the persistent spec gains the process and its port, the organisation's app gets the address the transport needs, a wake brings an older agent's machine config up to date, and an image with no terminal server is reportedYour 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 · CLI) `motir` carries the in-agent terminal server — a login shell as `node` in `$HOME/workspace` on a PTY that survives a dropped connection, resize, the relay's ticket verified, a sign-in check that reads only whether each coding agent's credential file exists, no stream byte logged, released by a changesetYour 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
- A terminal relay that dies without shutting down leaves its agent_terminal_connection rows open forever
- Open an instance beside the page and work in its terminal — sign in to the agent with your own account through the vendor's own flow, and the sign-in survives hibernationYour 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
- Release the `@motir/design-system` version that carries `renderMock` — push its `design-system-v<x.y.z>` tag, then pull the published package anonymously and confirm `renderMock` is exported
- (motir-core) The approve-to-merge gate exists only while CI is all green AND the card is In Review — today green CI alone raises it, so a card still In Progress is asked, and approving fails with IllegalTransitionError
- (manual) Merge the motir-core "Version Packages" pull request that bumps `@motir/design-system` for `renderMock`
- (motir-core · test) Story E2E — the built CLI prints a design card's prompt carrying the Motir-Design check and both branches, and a `renderMock` mock opens offline in a real browser with the package's parts styled and recoloured by palette
- (motir-core · test) Story integration gate — the coverage floor over `renderMock` and the design steps, the seam from a real `renderMock` output into the two-file publish door, and the guards a percentage cannot see
- (motir-ai · test) Story integration gate — the coverage floor over the changed rule, and the composed author prompt for a `code` leaf carries the conditional frontend rule and no unconditional `--el-*` instruction
- (motir-meta) Mirror the conditional frontend rule into `type-code.md`, re-word `type-design.md`'s `design` bullet to match, and record both in `MIRROR.md`
- (motir-core) The dispatched design steps tell the two kinds of project apart — build from `@motir/design-system` (with `renderMock` where the installed version exports it) when the project is on it, from the project's own components and theme when it is not, the no-system fallback, and never a migration
- (motir-ai) The shipped planner's FRONTEND rule becomes conditional — reuse the PROJECT's own design-system parts and semantic tokens; Motir's `--el-*` tokens only for a project on `@motir/design-system`
- (motir-core) `@motir/design-system` gains `renderMock` — the package's own parts rendered into ONE self-contained `.mock.html` under a given style, palette and type, with Tailwind compiled over the markup and `theme.css` inlined; the package's next minor version
- A design card builds in the project's OWN design system — from `@motir/design-system` when the project is on it, from the project's own components when it is not, and never in Motir's look by accident