Repository navigation
AgentMachinist 0.14.0
AgentMachinist 0.14.0 adds an end-to-end local workflow for solo developers and small teams. Start from a Git checkout, approve the exact Spec, and inspect a verified candidate with independent advisory Review. Integrate locally and publish to GitHub or GitLab when collaboration is useful.
Install or upgrade
uv tool install agentmachinist
# Existing uv installation:
uv tool upgrade agentmachinist
machinist --versionFirst local Task
machinist start "Handle an invalid timezone without crashing" --test-cmd "uv run pytest"
# Read the Spec and use the exact full SHA printed by start:
machinist approve --task T1 --spec-sha <full-spec-commit-sha>
machinist status T1
# Inspect the candidate diff and advisory Review before integrating:
machinist integrate T1
# Optional: matching origin and authenticated forge CLI required:
machinist publish T1 --provider gitlabLocal Tasks require at least one required Verification Gate and always complete independent Review. GitLab support covers issue import and MR publication through glab, including nested projects and self-managed hosts; it does not add hosted GitLab Spec CI or remote Approval. A local workflow can still use cloud models. Existing GitHub issue automation remains supported.
Changes
- Allow 30 minutes for the expanded real-Git CI test and package/release build jobs, keeping all checks required.
- Add the guided foreground local journey:
startsaves a Task and generates
its Spec;approve --task T1 --spec-sha <sha>continues verified Execute and
independent advisory Review. Status shows the local result and next action.
Initial setup needs Git, an installed Harness, and a verification command;
no origin, forge account, labels, daemon, or hosted workflows are required. - Add durable local Task IDs, exact repository/Task/Spec Approval, retained
candidate refs, reports, explicit amendments, cancellation, and retry. Local
Task Run construction reuses the dispatcher, lifecycle, custody, and
Verification engine. Local orchestration does not imply offline inference. - Add explicit local integration: fast-forward only, from a clean expected
base to the exact reviewed candidate, with persisted recovery intent.
Automatic and remote merges remain outside the controller's contract. - Make local publication optional and recoverable through GitHub PRs or GitLab
MRs. GitLab issue intake and MR publication use authenticatedglab, including
nested projects and explicit self-managed hosts. Exact repository/head
checks and leased pushes prevent silent destination changes or overwrites;
publication retries do not rerun successful Harness work or verification.
Native GitLab Spec CI and remote GitLab Approval are not included. - Fix GitHub setup PR's circular deployed-workflow prerequisite. Validate local
setup before creating the PR and check deployed readiness after merge.
Recognized partial onboarding resumes while preserving configuration. - Permit a fresh Review after a new successful Execute candidate, including
amendments, while blocking duplicate Review of the same successful head.
Print Review completion and finding counts instead of claiming it passed an
unimplemented severity policy. - Run rehearsal through the production local Phases, real Git, Verification,
Review, and integration. The default uses a deterministic fake Harness;
configured provider invocation remains an explicit--harnesschoice. - Accept Task bodies from files/stdin and preserve drafts on lint or creation
failure. Lint recognizes##and GitHub issue forms'###sections, respects
nested headings, and rejects empty or placeholder acceptance checkboxes. - Rename the daily Phase-attempt limit to
max_runs_per_day. Legacy
max_tasks_per_daystill loads with unchanged counting semantics; conflicting
aliases fail validation and effective configuration emits the canonical key. - Update the complete documentation set and interactive guides for local
onboarding, configuration and command namespaces, recovery, optional
publication, and GitLab support. Preserve earlier design records with
applicability notes and current references. - Reconcile a crashed Execute push from the remote Task branch as well as
GitHub's PR listing. When the listing lagged a push the controller had just
made, a fresh run failed its approved-head check and advised approving the
current head again, which could rerun the Harness on already-verified code.
That window now delivers the pushed implementation; the head-mismatch
messages say the remote branch moved after Approval and point at
machinist inspect. - One push step for fresh and resumed Execute runs. A retry after the
implementation commit re-enters the same leased push, observation, and
delivery instead of a separate resume-push path; a remote already at the
implementation is a no-op, one that moved elsewhere fails the lease. - Legacy GitHub
machinist approvetakes exactly one of--issue <n>or--pr <n>. The
positional target, which resolved issue-versus-PR ambiguity with its own
error, is removed; every documented example already used the flags.
Local workflow guide · Visual first-run guide
Release verification
The tag points to merged commit cf967186083f3195322bfb6fb0e76b7ae1a9b93d.
The release build and publication workflow passed all 1,413 tests, built and smoke-tested both distributions, published through PyPI Trusted Publishing, and verified an uncached install from PyPI. The release candidate CI passed on Linux and macOS with Python 3.12, 3.13, and 3.14, including coverage, minimum dependencies, packaging, and static checks.
The wheel and source archive were downloaded independently from GitHub and PyPI; both matched the attached SHA256SUMS. All 23 deployed documentation files matched the tagged source. The installed PyPI package passed the complete production local rehearsal with a deterministic fake Harness, including Spec, exact-SHA Approval, Execute, verification, Review, and local integration.
CI on the tagged, merged main commit also passed every job, including the complete Linux/macOS matrix and aggregate CI gate. Both CodeQL analyses passed on the same commit.