Skip to content

AgentMachinist 0.21.0

Latest

Choose a tag to compare

@vscarpenter vscarpenter released this 16 Nov 00:38
2de64f8

AgentMachinist 0.21.0 puts the decision first when you inspect a local Task or revise a plan. It also refreshes the project's dependencies.

Read the decision before the details

  • machinist inspect T1 opens with a bounded decision summary: the paths the Task changed, each Gate outcome, high-severity advisory Review findings, and the next actions you can take. The full plan, diff, checks, and history follow, and the actions repeat after them.
  • After machinist revise T1 --feedback "...", AgentMachinist shows a bounded difference between the two Spec commits before the revised plan. A revision that changes only line endings says so. Every revised plan still needs fresh Approval.
  • The summary counts results before it truncates them, so omitted failures and findings stay visible. It leaves out an Execute report whose commit does not match the candidate instead of showing it as a passing check.

Recovery

  • When approve or continue meets a stopped local Phase, the message names machinist retry --task T1 --phase execute. It used to print the GitHub issue form, machinist retry 1.

Documentation

  • The documentation now lives at https://agentmachinist.com/docs/.
  • The first-run guide covers the local workflow only. The GitHub Actions setup has its own page.
  • Two new pages: a reader glossary, and a local Task lifecycle diagram that shows each state machinist status prints and the command that moves it.

Dependencies

  • The lockfile moves to Click 8.5.1, pydantic 2.14.3, and pytest 9.2.0. The pinned development tools move to Ruff 0.17.5, mypy 2.4.1, and Hatchling 1.33.0. Runtime requirements keep their existing minimums.
  • The managed Spec workflow template now pins astral-sh/setup-uv v10.3.3. If your repository runs Spec in GitHub Actions, run machinist sync-workflows after you upgrade.

Upgrade:

uv tool upgrade agentmachinist
machinist --version

Python 3.12 or later is required.

The release workflow verifies the exact version, builds and smoke-tests the wheel and source distribution, and publishes using PyPI Trusted Publishing. Distributions and SHA-256 checksums are attached after successful publication.