Releases
amenbo release notes.
amenbo’s release history. Install and update instructions are on Start; what changed in each version is in the notes below.
A project can now carry an icon image, so it is picked out by its face rather than by a colour and a letter. The changes from 20.0.0 and 21.0.0 also landed by this version.
A category can now be set to take several answers on one record, so work that sits on two sides is recorded as both. The decision-record work that started in 16.0.0 also landed by this version.
The categories you already use on tasks now go on decisions too, and the decision list can be narrowed by one. Removing a category value asks where the tasks that carried it move to.
An AI connected over MCP can be shown a project's backlog and add tasks to it, without ever opening the folder. You choose, per app, which projects it reaches.
Export, backup and restore now stop at the window a plugin was launched in, and an export file is one moment's records. One shape change in what amenbo agent --json returns.
Narrowing a search is now two knobs instead of one, so the comments on decisions alone is a question you can ask. Every hit also says where its record stands.
Creating a task now has an end you mark yourself. Until you mark it, the task sits on the board like any other, but no AI takes it and no one can reserve it.
Creating a project now asks for the folder it lives in, because an AI reaches a project through a folder. The last folder can now be unlinked, and a project left without one is reported until you deal with it.
Searching for a word keeps you waiting less, and the more you have recorded the more it shows. What comes back is the same as in 5.0.0.
Words move out of the list filter and into the new `amenbo search` command, which answers with the places a word appears rather than a list of records. The GUI gains a search of its own. Words in `--filter` no longer work — read the update section first.
amenbo hands you the text that makes an AI tool read amenbo at the start of every session, a plugin's switch and its settings now sit in one row per project, and waiting notifications can be pushed through. The stored data format goes up — read the update section first.
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.
Every plugin now has a single per-project switch, and the row names the projects it runs in. Settings and credentials are carried in the backup, and the stored data format goes up — read the update section first.
The interface went from 2 languages to 19, picked up from your OS setting and changeable at any time. On Linux the GUI is now a single AppImage, so the install steps changed.
Creating a project now lays out three moves: open a terminal, paste the request to your AI, watch the tasks land on the board. The same three sit on a board with nothing on it yet.
A superseded decision record now points at what replaced it, and the badge says the decision's status. Classifications respect the project boundary. The CLI filter `current:` becomes `superseded:`.
Install a plugin and it runs when something happens to a task. Teams can serve plugins from a catalog of their own. On the CLI, `--actor` is now required on every command.
Press the update banner and the app swaps itself to the new version in place. Installs now go to your own user location, so no admin rights are needed. CLI-only setups get a one-command update and a rollback.
Give a task a start day and, until that day arrives, it cannot be started and drops out of the ready-to-start filter. It stays visible in the list, so you keep a view of what is coming. Start days can be filtered on, and a dismissed update notice now stays dismissed.
Inbox @me now carries only the comments addressed to you, so the unread badge counts things that actually need you. List rows also reach all four statuses, and body options can read their text from stdin.
Collapse or resize the left sidebar, see open tasks and undecided decisions as badges, and link a task to the commit that implemented it.
amenbo ids like AMB-T-… can now be caught by a git hook before they land in a commit. If you already run husky or another hook tool, amenbo sits alongside it rather than replacing it.
Intel Macs now have an installer of their own. The guidance amenbo leaves in a bound folder is also brought up to date after you update amenbo, so an AI agent started there no longer reads the old wording.
The one-time data update now shows what it's doing instead of looking frozen, and it backs your store up first. Backups from older versions can be restored, restores report progress, and open lists stop going stale.
Clicking the "Amenbo" wordmark at the top of the app now opens the product page (amenbo.work) in your default browser.
Reordering projects in the sidebar now takes and persists. Running the app and CLI at once no longer corrupts your state. macOS installs always land in /Applications.
The GUI and CLI now ship in a single installer. amenbo tells you when a new version is out, and makes reservation conflicts on the same task clear.
Tidying up the desktop app's sidebar: reorder projects, per-project open-task counts, and the onboarding screen turned into help.
amenbo's first release is out. The CLI and the desktop app run on macOS / Windows / Linux.