moo

Develop inside moo machines so runtime state (database, packages, services) is isolated per branch and versioned per commit. Use when starting work on an issue, branch, or feature in a repository that uses moo (has a moo.toml or the user mentions moo), and for any git workflow — checkout, commit, merge, bisect, parallel attempts.

Give a moo machine a clickable Linux desktop served in the browser, or provision it with the common agent toolkit (dev tools, Node.js, Chromium). Use when the user wants to see or click around an app running in a moo machine, asks for a desktop, GUI, VNC, or browser view of a machine, or wants a machine equipped for browser-based testing.

Set up moo for a project by creating its golden base image and a provisioned baseline machine. Use when starting to use moo in a repository, when the user asks to create a golden image, set up moo, provision a base environment, or start from a blank VM.

Produce real, human-checkable evidence from a moo machine that an implemented change actually works — videos for UI, raw API request/responses for backends, queries with outputs and plans for databases — before claiming completion. Use after implementing any feature or fix in a project that uses moo, or when the user asks to verify, prove, or show evidence that something works.