miniforge-ai / miniforge

# Miniforge
Write a spec. Get a pull request.
Miniforge is an autonomous software factory. You describe what you want — in
plain English or structured EDN — and miniforge plans the work, writes the code,
runs the tests, reviews itself, and opens a PR. No prompt engineering. No
copy-paste. Full SDLC.
## Before and After
 [code] 
## How It Works
Miniforge runs four nested control loops — a team of agents does the work,
a tight inner loop enforces quality at every step, a monitor resolves
reviewer feedback after delivery, and meta-agents govern the whole operation.
**Team loop** — specialized agents collaborate through phases, like a dev team
handing off work:
 [code] 
**Inner loop** — inside each phase, the agent generates an artifact, validates
it against policy gates, and repairs failures automatically:
 [code] 
**Observe loop** — after Release creates a PR, the monitor loop runs
autonomously for up to 72 hours:
 [code] 
**Meta loop** — governance meta-agents supervise the entire operation at a
semantic level. Any meta-agent can halt the factory floor:
 [code] 
Policy gates govern every transition. Budget limits (tokens, cost, time)
enforce hard stops. All decisions produce evidence bundles for traceability.
## Quickstart
### Prerequisites
- macOS, Linux, or Windows — see Platform Support
 for the install path on each. Native Windows is in beta; WSL2 and Git Bash
 are first-class today.
- Babashka (Mac/Linux:
 Homebrew or `bash <(curl …) --static`; Windows: `scoop install babashka`)
- An LLM backend: OpenCode CLI, Claude Code
 CLI, or Codex CLI. Provider API keys for
 miniforge agent runs are configured through OpenCode.
- An OCI-compatible local container runtime (see below). Podman
 is the recommended default; Docker is supported.
 Other Docker-CLI hosts (Colima, OrbStack) work as `:runtime-kind :docker`.
### Install and Run
 [code] 
`bb bootstrap` installs the development dependencies (Java, Clojure CLI,
clj-kondo, Polylith, markdownlint), configures the repo, prefetches the
coverage tool used by `bb ccov`, and on macOS brew-installs Podman and
initializes a default `podman machine`. Linux users install Podman via
their distro package manager (`apt install podman`, `dnf install podman`,
etc.); Docker users can stay on Docker by setting
`MINIFORGE_RUNTIME=docker` or `:runtime-kind :docker` in config.
To check the resolved runtime: `mf doctor` (which now reports the
selected runtime + version + override hint) or `mf runtime info`
(prints the descriptor as data).
See the Quickstart Guide for a detailed walkthrough.
### Write a Spec
A spec is a description of what you want. Two fields are required:
 [code] 
Specs can also be written as Markdown with YAML frontmatter. See
Writing Specs.
### Run the Demo
 [code] 
The demo is a Bash script. On native Windows, run it from Git Bash or WSL2 —
or invoke the underlying workflow directly with `mf run
examples/demo/add-utility-function.edn`. See Platform
Support for details.
See Demo Guide for a guided walk