Agentplane 0.3.2 is a cleanup release, but in the good sense. A bunch of things that had been treated like “yeah, that’s annoying, we know” finally got fixed properly.
The biggest wins landed in upgrades, direct-mode task closure, and framework development inside the Agentplane repo itself.
Upgrades became more direct
Before 0.3.2, upgrade behavior still carried older assumptions from an earlier model. By that point the framework already owned the managed files, but the UX had not fully caught up.
0.3.2 shifts the default in a more practical direction:
- managed framework files now apply by default,
doctorgives better guidance when a repository is only partially upgraded,- docs explain more clearly which files belong to the framework and which local file is still meant for local incidents and overrides.
The practical result is simple: fewer half-upgraded states, less guessing, less “why is this repo in a weird hybrid mode?” energy.
Finishing a task no longer dirties the tree by default
This release also tightens the direct workflow.
In normal direct-mode use, finish now records task metadata and creates the close commit automatically unless you opt out. That removes a long-running annoyance where the task looked done but the repo still had a dirty README sitting there.
This is a small change, but I would not call it minor. A task marked done should leave the repo looking done.
Framework development got less misleading
One of the most practical changes in 0.3.2 is for people working on Agentplane itself.
If agentplane from PATH is launched inside the framework repository, it now hands off to the repo-local binary by default instead of quietly using an older global install. There is still an opt-out, but the default is finally closer to what a developer expects.
That matters because mixed runtime sources create very confusing failures:
- the docs in the checkout say one thing,
- the code in the checkout says the same thing,
- but the executed binary still behaves like an older version.
0.3.2 does not erase that class of confusion completely, but it cuts out the worst trap.
Release and docs discipline also improved
The same release also cleaned up the release path and the agent-facing docs layer.
It fixed a case where release apply --push --yes could hang after creating the commit and tag, improved the test coverage around that path, and aligned the main bootstrap surfaces so agents see one clearer startup path instead of several competing ones.
That may sound internal, but users feel it anyway. A tool is easier to trust when its docs, startup help, and release behavior stop drifting apart.
Practical outcome
For most users, 0.3.2 means:
- upgrading older or partially patched repositories is easier to recover,
- finishing work in direct mode leaves fewer cleanup surprises,
- framework contributors are less likely to accidentally run the wrong binary,
- startup guidance across CLI and docs is more consistent.
This is not a flashy release. Fine. It removes real friction from the actual workflow, which is more valuable.
Upgrade note
There are no breaking API or workflow-mode changes in 0.3.2.
Framework developers should update their installed CLI if they want the new repo-local handoff behavior inside the framework checkout. Older initialized repositories should run agentplane doctor after upgrade and follow the suggested recovery command if the managed policy tree is incomplete.
The formal source record remains the release notes at /docs/releases/v0.3.2.