amenbo

amenbo 22.0.0 — a project can carry an icon image

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.

Projects can now carry an icon image. The changes from 20.0.0 and 21.0.0 also landed by this version.

A project can carry an icon image

Until now a project was told apart by its colour and the first letter of its name. As the number of projects grows, colour alone stops being enough to pick one out.

On the Project settings screen, press Choose image…, pick a file, and press Save. The image then shows in the sidebar and on the project tabs.

StateWhat is shownHow to change it
no image registeredthe project’s colour and the first letter of its nameChoose image… registers one
an image registeredthe registered imageChoose image… swaps it; Remove image returns it to the colour and letter

The same slot exists for the human’s and the AI’s own faces, on the Settings screen (also Choose image…).

A record can be reached by its number alone

Tasks and decisions carry a number. You no longer have to type the whole AMB-T-… form; the number alone reaches it.

Search takes a bare number:

$ amenbo search 1
1 hit(s)
  [title] AMB-T-… The crash on both handsets
      todo
      The crash on both handsets

Filtering uses number:. A bare number passed to a filter is refused, and the refusal says how to write it:

$ amenbo task list --filter 1
Error: filter '1' must be in key:value form — to filter by the conversational number, write `number:1`

$ amenbo task list --filter number:1
1 task(s)
  [ ] AMB-T-…  The crash on both handsets

The search box on screen behaves the same way: a bare number brings up that record.

A category value can be closed instead of deleted

Deleting a value that is finished with takes the value off every record that carried it, so you can no longer tell which ones were in it. Closing it drops it from the choices offered for new records, and leaves the records that already carry it untouched.

The category has to be nominated as one whose values can be closed first:

$ amenbo dimension update Release --closable true
✓ Updated dimension: AMB-DIM-…

$ amenbo dimension value-close Release v1
✓ Closed value: v1 (AMB-DIMV-…)

A closed value drops out of the listing:

$ amenbo dimension show Release
AMB-DIM-…  Release (d1)
kind: single, ordered, closable
1 value(s)
  AMB-DIMV-…  v2 (v2)

Narrowing by that value still finds the records that carry it:

$ amenbo task list --filter "dim:Release=v1"
1 task(s)
  [ ] AMB-T-…  The crash on both handsets

Reopening puts it back among the choices:

$ amenbo dimension value-reopen Release v1
✓ Reopened value: v1 (AMB-DIMV-…)

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)
  • 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.

The stored data format moves up — the first launch on this version migrates it, and a backup from before the migration is kept automatically. Once migrated, an earlier version can no longer open it. The GUI and the CLI are updated together by the same installer, so do not leave one of them on the old version.

New here? See Start.