amenbo 5.0.0 — Searching for a word tells you where it is written
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.
Looking for a word has moved to its own command, and what comes back is the places the word is written. Writing a word into --filter no longer works, so read the update section before you upgrade.
Searching tells you where a word is written
The new amenbo search command answers with places, not with a list of records. One line is one place, and it says which surface the word was on: a title, a body, a comment, a dimension’s label, or an attachment’s file name.
$ amenbo search books
1 hit(s)
[comment] AMB-T-… Send the monthly invoices in one batch · AMB-TC-…
Close the books first, send the next working day
- Part of a word is enough — searching for
invoicefinds “Send the monthly invoices in one batch”. - Ways of writing the same thing are treated as the same — matching is case-insensitive, and Japanese full-width and kana forms are normalised, so
pdffinds PDF. - A reference number goes in the same place — type something like
AMB-T-…and that record comes back first. - You can narrow to one side —
--kind taskor--kind decision. Add--filter "status:todo"and the structural narrowing from the lists stacks on top, with the same syntax.
Words are no longer a filter key
--filter no longer accepts text:. Words belong to search.
$ amenbo task list --filter "text:retention"
Error: words are not a filter key — `search <word> …` finds where they are written (add --filter for the structural narrowing)
The GUI has a place to search across everything
“Search” in the left sidebar looks at tasks and decision records at once, and groups what it finds by the place the word is written.
- Press a hit and the record opens beside it — you see which surface the word was on and read the record from there.
- “Everything / Tasks / Decisions / Comments” keeps one side — the rest drops away.
- Structural narrowing sits next to the word — type something like
status:todoin the field beside it, with the same syntax as the lists.
The board’s own narrowing has a field of its own too — it reaches places the card does not show, so a word written in a comment keeps that card on the board.
Smaller things
- “Check for updates” on a plugin goes and checks — pressing it used to do nothing at all sometimes. It now also shows how current the catalog it answered from is.
amenbo updatelooks at the latest every time — it used to be able to answer from what it had checked a moment earlier.- What you type is left alone on macOS — the first character in a field used to turn into a capital, and the underline from an in-progress conversion could stay behind.
Before you update
- The stored data format goes up — it migrates automatically the first time a newer version opens it, and a backup is taken beforehand. 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).
- Replace
text:in--filterwithsearch— in your own scripts, and in the instructions you hand your AI.
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
amenbocommand 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.