amenbo 3.1.0 — A plugin setting can offer you the choices, and an AI is handed the plugins it can call

Settings you tick instead of type, a clear line between "nobody has picked yet" and "none of them", the plugins available in a folder handed over at the entry point, and update checks that notice a change inside.

A plugin setting can now offer you the choices to pick from. What an AI is handed at the entry point, and which plugin updates reach you, have changed too.

A plugin setting can offer you the choices

The plugin’s author lists the choices, so you pick instead of typing a value — less guessing at what to write.
In the GUI, one checkbox per candidate — the plugin’s settings form draws them all, and “Save” stores what you ticked.
On the CLI, comma-separated — amenbo plugin config set worktree events task.done,task.rejected. amenbo plugin config get prints the candidate list together with what is in force.
Anything not among the choices is refused at the point of entry — a typo is never stored for you to find later.

$ amenbo plugin config set worktree events task.created
Error: 'task.created' is not one of the choices 'events' offers
Hint: Choose from: task.done, task.rejected, task.blocked (comma-separated). `none` chooses none of them, and an empty value goes back to the default.

“Nobody has picked yet” and “none of them” are two different answers

The two look alike, but what reaches the plugin differs. With nobody having picked, the author’s default stands; with none of them chosen, the plugin is handed nothing.

The state	What the screen shows	What `plugin config get` prints
nobody has picked yet	chipped “Default”, with the default candidate appearing ticked	`task.done (the default — nothing set here)`
picked from the candidates	the picked ones are ticked	`task.done,task.rejected`
decided on none of them	everything clear, chipped “None chosen”	`(none of them)`

You can go back to the state before you picked — “Restore the default” on screen, or an empty value on the CLI, brings the author’s default back.

An AI is handed the plugins it can call in that folder

The plugins that run in the project come with amenbo agent --json — that one call already hands an AI how to work with amenbo, and it now lists them too. There is no separate plugin listing to fetch: one call at the start says what can be called here.
When to reach for a plugin, and how to call it, come along — if the plugin’s author wrote them.

When nothing is listed, the reason comes with it — whether no plugin is enabled, or the folder is not linked to a project.

"pluginsEmptyBecause": "no plugin is enabled in this project — installing one never turns it on; `plugin enable <name>` opens its gate here"

An update that only changed what is inside now shows up

A new setting field, a change in which events a plugin receives, a description written for AI — in updates like these the plugin’s executable does not change at all. amenbo plugin update --check used to look only at the executable, so this kind of update never reached you. It now looks at the contents, so it shows up.

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.