amenbo 10.0.0 — a plugin reaches only the project it fires for

A plugin is given a window, and export, backup and restore now stop at it. We are sorry for the behaviour that stood through 9.2.0. One shape change in what amenbo agent --json returns — read the update section before you upgrade.

Export, backup and restore stop at the plugin’s window

amenbo hands a plugin a window: the project it fires for, and nothing else. Through 9.2.0, three commands did not consult that window. Called from inside a plugin, export, backup and restore acted on every project on the device — and restore writes rather than reads, so it could replace the stored records themselves.

In 10.0.0 the call is refused.

Error: export acts on this whole device, and a plugin reaches only through the window it fires in (AMB-P-…) — a window no argument widens. Nothing outside it was yours to read or to replace: the ids in the payload name what you were launched for.

backup and restore refuse the same way.

Running these commands yourself is unchanged, and so is an AI you have entrusted a folder to. Only the call made from inside a plugin is refused.

An export is one moment’s records

Records can be added while an export is running. Through 9.2.0 a comment added after the export started could land in the file while the task it hangs off did not, leaving a file that pointed at something not in it. In 10.0.0 the whole exported file is one moment’s records.

Plugin commands appear at the step where they are used

amenbo agent --json is what an AI reads to know how to work in a folder. Install and enable a plugin, and its command lines now sit on the step they belong to. From the worktree plugin:

{
  "id": "cut-per-task",
  "step": "Cut a worktree per task, whenever the work will produce commits. ...",
  "tools": [
    "amenbo plugin run worktree start <task-id>"
  ]
}

The AI no longer has to work out how to call the plugin at that point — the call is on the step.

If you already have the worktree plugin, amenbo plugin update worktree swaps it.

A short commit SHA is refused with how to build the full one

amenbo task commit add takes only full-length SHAs. The refusal now carries how to expand a short one.

$ amenbo task commit add AMB-T-… 4a73991 --actor ai
Error: a commit sha must be full-length lower-case hex (40 for SHA-1, 64 for SHA-256) — not a short sha, branch, tag or revision
Hint: `git log --oneline` prints the short form. Expand it with `git rev-parse <short sha>` and pass what that returns — amenbo never runs git itself.

Before you update

One shape change in what amenbo agent --json returns. The instructions you hand your AI need no editing, because they come from amenbo agent --json itself. Only your own scripts that parse that output are affected.

agentCycle went from a list of sentences to an object. It now holds description, which says how to read the steps, and steps. Each step carries an id.

The stored data format does not change, so data from the previous version opens as it is.

Getting it

Open the installer for your OS from the latest release. No admin rights are needed.

• macOS — .pkg, one for Apple silicon and one for Intel (GUI and CLI come together; first open shows a Gatekeeper prompt: right-click → Open)
• Windows — setup .exe (GUI and CLI come together)
• Linux — the GUI is an AppImage; the amenbo command comes from the CLI installer

To update: on the GUI, the “a newer version is available” banner applies it in place. If you installed only the CLI, amenbo update --apply swaps it.

New here? See Start.