amenbo 3.0.0 — A plugin is switched on per project, and its settings travel with your backup

Plugins are now switched on one project at a time, and where their settings live has changed. Read the update section before you upgrade.

A plugin’s switch is one per project

• The per-device switch is gone — there used to be two kinds of switch: one that opened per project, and one that opened for the whole device, and the plugin’s author decided which one a plugin got. Now every plugin has a single per-project switch.
• The row names the projects it is on in — instead of a yes/no, you see the names of the projects where the plugin runs. Turn one off and you can see it still running in the others. If no name is listed, it runs nowhere.
• You can also switch it from a project’s settings — you reach the same switch from either end: “which projects does this plugin run in” and “which plugins run for this project”. You no longer have to go hunting through a plugin list to turn something off.
• Installing no longer asks which project — installing aims at no project, so it doesn’t ask. The screen says that nothing runs yet, and where to turn it on.
• Turning it on is itself the permission to run it — the separate consent prompt is gone.
• The CLI names projects too — each row of amenbo plugin list shows the projects the plugin runs in. amenbo plugin enable / disable move the switch for the project of the folder you are standing in.

Settings and secrets now travel with your backup

• A restore brings them back working — restoring from a backup used to come back with the settings gone and every credential to type in again. The backup now carries the whole of a plugin’s state.
• Values belong to a project — --scope is gone from amenbo plugin config set / get; they read and write the value for the project of the folder you are in. The settings form in the GUI edits the project it is showing.

A plugin’s help now comes from the plugin

amenbo plugin run <name> --help now prints that plugin’s own usage. It used to hand back amenbo’s own text, so there was no way to find out how a plugin worked.

Every word after the name belongs to the plugin. Flags meant for amenbo itself (such as --actor) go before the name.

amenbo --actor ai plugin run worktree --help

The Linux CLI runs on older distributions

The amenbo command would not start on somewhat older distributions such as Ubuntu 22.04. The GUI (AppImage) ran there, so you could end up with only half of it working on the same machine.

Before you update

• The stored data format goes up — it migrates automatically the first time the new version opens it, and a backup is taken first. Older versions cannot open it afterwards, so don’t leave either the GUI or the CLI on the old version (the same installer updates both).
• Plugins you had on for the whole device move to per-project — anything that used to run in every project on that device comes up switched on in each of them. Turn off the ones you don’t want.
• Drop --scope if you were passing it — amenbo plugin config set / get no longer accept it.

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.