Repository navigation
v0.19.0
0.19.0 adds a built-in Goose Harness adapter and clearer first-run guidance found by walking the first-Task path as a newcomer. Human Approval, exact-SHA binding, and controller ownership of Git operations remain unchanged.
- Add a built-in Goose adapter (
harness.name: goose). Spec and Review run
goose run -q --no-session --no-profile --with-builtin developer, and
Execute runsgoose run --no-session. The developer builtin can also write
files, so read-only custody is advisory and the controller's postconditions
enforce it, as for OpenCode. - Set
GOOSE_MODE=autofor every Goose run. The approval modes wait for a
confirmation that a headless Task Run cannot give. - Keep Goose out of first-run discovery. pressly/goose, a Go database
migration tool, installs the samegooseexecutable, so choose Goose with
--harness goose. - Goose has no managed GitHub Spec CI profile and no non-interactive auth
probe. Workflow projection refuses it with the local-dispatch recovery, and
doctorasks you to verify its login yourself. - Adapters can pin non-secret environment variables with
environment_overrides()and opt out of first-run discovery with
auto_select = False. - Point
config showandconfig setatmachinist startwhen neither
machinist.yamlnor saved local settings exist, instead of recommending
GitHub onboarding. Neither command creates a file. - Align help text with the local workflow:
onboardis optional GitHub
automation,amend --taskstarts from a reviewed candidate, and
retry --freshnames both defaults. - Document that the controller ignores global Git identity. Set
user.nameanduser.emailinside the repository, or Spec and candidate
commits use the AgentMachinist identity. The first-Task example now does
this and clones the repository before copying.
Upgrade:
uv tool upgrade agentmachinist
machinist --versionGoose is never chosen automatically; select it with machinist start --harness goose. If your commits should carry your name, set git config user.name and git config user.email inside the repository, because the controller ignores your global Git identity.
The release workflow verifies the package, publishes through PyPI Trusted Publishing, attaches wheel and source distributions with SHA-256 checksums, and checks an isolated install of the published version.