amenbo

amenbo 2.1.0 — Follow a superseded decision to the one that replaced it

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:`.

This release is about how decision records are shown, together with fixes around task classification. One filter for decision records is gone from the CLI — read “Before you update” if you filter with current:.

A superseded decision points at what replaced it

  • The listing row names the record that replaced it — a superseded record now reads “superseded by D-363” in the list. You can follow it from there, without opening the record.
  • The badge says the decision’s status — proposed, accepted, or rejected. It used to say “superseded” instead, so once a record was superseded you could no longer tell whether that decision had been accepted or rejected. A record that was rejected and later superseded shows both.
  • The machine-readable output carries it too — each row of amenbo decision list --json includes the number of the decision that superseded it.

Classifications respect the project boundary

  • The same axis name can be used in more than one project — if an axis named, say, “Phase” also existed in another project, naming it by name was refused as ambiguous. It now resolves as the axis of the project the task belongs to.
  • A classification from another project is refused — it can no longer be attached. Moving a classified task into another project is refused as well, unless the destination has that same classification.

Before you update

  • current: is gone from the decision-record filter; use superseded: — still in force is superseded:no, and superseded is superseded:yes. The old form is refused with unknown filter key 'current'. The --json output no longer carries current; each row carries superseded_by instead, the number of the decision that superseded it. If an AI runs your commands, have it re-read the output of the amenbo agent command and it will use the new form.

Getting it

Open the installer for your OS from the latest release. GUI and CLI come together, and no admin rights are needed.

  • macOS — .pkg, one for Apple silicon and one for Intel (first open shows a Gatekeeper prompt: right-click → Open)
  • Windows — setup .exe
  • Linux — .deb / .rpm

To update: on the GUI, the “a newer version is available” banner now applies it in place. If you installed only the CLI, amenbo update --apply swaps it.

New here? See Start.