About this project
Mill is a guardrailed desktop workbench for automations, a knowledge board and connectors, built as a single binary from Go and React (Wails v3). The README frames the motivation as closing the gap between what an AI assumes about a system and the system's verified state: humans and agents work from the same view, and each action that reaches outside the machine is previewed and gated before it happens. Mill keeps data in local files, does not call an AI API of its own, and does not phone home.
Documented surfaces, all reachable by a person in the app and by an agent over MCP under the same guardrails:
Home shows what ran, what is waiting for approval, and the most-used workflows. Workflows are built on a canvas from triggers and steps connected in order; the seeded example is a Clipboard to Markdown flow that reads copied HTML, converts it, writes Markdown back to the clipboard and notifies the user. Configure holds Integration entries so multiple workflows can share one base URL and auth definition, edited in one place. Atlas is a board where dropping a folder of markdown files turns each file into a card that updates itself when edited outside Mill. Activity is a searchable log of runs, guardrail decisions and agent calls. Review lets a workflow run resume after Mill crashes or restarts instead of vanishing. Secrets are picked, never typed: workflows carry the name of a secret and Mill resolves the value only when a step runs. Extensions add board objects, workflow steps, commands, secret sources or views as a folder of two files, and run only with the user's consent.
The README states an inventory of 54 step types, 8 board object kinds, 13 extension contribution families and 46 MCP tools. A companion browser extension can be paired so Mill can replay recorded steps in the user's own signed-in session.
Installation is by cloning and building rather than a hosted service or account. Requirements are Go, Node, the Task CLI and the Wails v3 CLI; task setup:hooks installs pre-commit hooks mirroring CI, and task install:app builds Mill and installs it to /Applications, while task dev runs a hot-reloading development copy. Prebuilt macOS releases are published on the releases page. A short getting-started path covers rebuilding the seeded workflow, putting a card, table and diagram on a board, and pointing an agent at Mill over MCP.
Documentation ships in three forms: a Docs view in the app, the userdocs directory on GitHub, and llms.txt plus llms-full.txt for agents. Bugs and feature requests go to GitHub issues, with the bug template asking for the build badge the app displays; pull requests follow CONTRIBUTING.md and vulnerabilities are reported privately per SECURITY.md. Licensed under Apache-2.0.
Comments
0 Rating appears after 10 ratings
Sign in to join the discussion.