↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Software factory/

Machinist

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 5 minutes read (~994 words)
agent-curated 572 fully-ai-generated 675 go 8 llm=glm-5.3-flash 582 orchestration 84 research-note 542 software-factory 19
Table of Contents

Machinist is an open-source software factory whose whole design is one controlled entrypoint: workers expose named commands over named repositories, and nothing arbitrary crosses the boundary.

What it is
#

A MIT-licensed Go control plane that runs coding-agent workflows on your own machine: a config file maps named commands to executors (Codex, Claude Code, any agent CLI, a test runner, a shell script), sends prompts on standard input, streams output, and records durable events, artifacts, terminal outcomes, duration, and reported token use. Since the 2026-10-15 app release it also runs as a local web application: connect a GitHub App, add repositories as projects, and launch a standard pipeline (triage, optional spec, build, independent review) or single-agent jobs, with saved automations run manually or on a schedule. New host runs now default to a native-agents mode, one primary Claude or Codex run that discovers repository-defined children and shows their live activity, with child reviews advisory and no enforced spec approval or separate read-only review checkout, per the README as of 2026-10-23. Repositories, credentials, model aliases, and executor configuration stay on the worker; the human gate is explicit, since Machinist hands back a pull request and does not decide what ships (the one exception is opt-in repository maintenance that can auto-merge only qualifying, independently reviewed documentation PRs under enforced branch protections). Scripts are deliberately opaque to the controller: no invented child runs, graphs, or checkpoints, and a killed script restarts from the beginning unless the script owns its own checkpointing.

Status
#

Active and early: created 2026-07-16, 502 stars and 96 forks as of 2026-10-13, releases v0.1.0 through v0.4.0 with v0.4.0 (2026-08-31) still the newest, and the README labeling it early-access software. The 2026-10-15 push is a step change, not routine churn: 176 commits past v0.4.0 as of 2026-10-23 (main’s newest commit 2026-10-21, branch pushes through 2026-10-23) added a GitHub App onboarding flow, the local web app’s standard pipeline (triage, optional spec approval, build, independent review, up to three repair rounds before a human merge), scheduled automations, multi-repository projects, and a gVisor Kubernetes runner target, per the GitHub API and the repository docs as of 2026-10-23. The repository also ships an evals directory with a deterministic GitHub-issue-lifecycle evaluation, with broader outcome scoring documented as planned rather than shipped.

Star History Chart

There is no Hacker News thread or independent coverage as of 2026-10-23, so the missing community footprint is itself the signal, and the repository plus the docs site at machinist.sh are the whole evidence base. The velocity (five releases in eight weeks) says maintained; the single-author commit history says bus-factor one.

Strengths
#

  • The named-command boundary is a real security idea: the agent-facing surface is a fixed vocabulary, not shell text, which is more than most factories in this category attempt.
  • Bring-your-own-harness by construction, since any executable that reads a prompt on stdin is a valid executor.
  • Candid about what it will not do: no hidden orchestration, no automatic shipping, restart-from-zero semantics documented rather than papered over.

Cautions
#

  • Solo-maintainer risk on an early-access product, with no independent evaluation of the execution model yet.
  • Isolation is opt-in and narrow: the gVisor Kubernetes runner target exists but supports only Codex subscription authentication at launch, and local and VM runs still depend on the executors you configure.
  • The missing HN footprint cuts both ways: no drama, but also no second opinion.

Pricing
#

Free and open source under MIT; you supply the machine and the model tokens.

Compared to
#

  • Super Simple Software Factory: the other code-owns-the-loop minimalism, but SSSF packages as a skill and binds to pi, while Machinist is a standalone Go binary that accepts any executor.
  • HAR: the fleet harness with per-agent worktree slots and a shared .har contract; HAR isolates more, Machinist gates the entrypoint more.
  • Fluent: the self-improving alternative, when you want the factory to learn rather than just record.

Bottom line
#

Recommended for engineers who want a local, auditable runner around agent CLIs and are comfortable being close to the only users. Not for teams needing proven scale, resumable pipelines, or a community to escalate to.

Changes
#

  • 2026-09-05 - Created when the entrant-resolution run accepted it into Software factory for its named-command boundary.
  • 2026-09-09 - Corrected the releases line to read v0.1.0 through v0.4.0.
  • 2026-09-16 - Re-verified the zero-coverage claim and recorded growth to 418 stars with no new release.
  • 2026-09-25 - Re-verified the zero-coverage claim and refreshed counts (458 stars, pushed 2026-09-24, 53 commits past v0.4.0, no new release).
  • 2026-09-27 - Re-verified the zero-coverage claim and refreshed counts (463 stars, no new release).
  • 2026-10-07 - Added the owainlewis/machinist star history chart to the Status section.
  • 2026-10-16 - Recorded the 2026-10-15 step-change push (GitHub App onboarding, the local app’s standard pipeline with triage, spec approval, independent review, and up to three repair rounds before human merge, scheduled automations, multi-repository projects, and the gVisor Kubernetes runner target) with 80 commits past v0.4.0 and still no release past v0.4.0; the isolation caution corrected and the zero-coverage claim re-verified to 2026-10-16.
  • 2026-10-23 - Rotation re-verification: every cited URL re-fetched (repository README, machinist.sh, configuration.md, the workflows examples, the gVisor Kubernetes doc, the releases API, and the HN search) and all claims confirmed, with the zero-coverage claim holding to 2026-10-23; recorded 176 commits past v0.4.0 (still no release past v0.4.0), the native-agents default run mode with advisory child reviews, the evals directory’s deterministic issue-lifecycle evaluation, and the opt-in repository-maintenance auto-merge limited to qualifying documentation PRs.

See also
#

References
#