amenbo 2.3.0 — The interface comes in 19 languages, and Linux is now an AppImage

The interface used to come in 2 languages; it now comes in 19. If you are on Linux, read the install section — how amenbo is distributed there has changed.

The interface now comes in 19 languages

• It opens in your OS language — the language is taken from the OS setting, and first-run setup appears in that language too.
• You can pick one from a list — each language is listed under the name it calls itself, and you can change it from the settings at any time.
• Dates, times and counts follow that language’s conventions — relative phrasing like “3 days ago”, plural forms for languages where one item and two items take different forms, and each language’s own brackets and quotation marks.
• Refusal messages come in the same language — when another session already reserved a task you tried to take, when a backup or an update cannot proceed, and the explanations on the plugin screens.
• With nothing set, it now falls back to English — it used to fall back to Japanese. If you are already using it in Japanese, it stays in Japanese.

Opening a project that is already on this device, from the first screen

The “Getting started” screen used to only display a command, and you had to open a terminal and type it yourself. It now lets you pick a project and link a folder to it, right there. Once the folder is linked, the first-loop steps appear as they do elsewhere.

Linux is now a single AppImage

• .deb / .rpm are no longer distributed — the GUI is a single AppImage file and needs no admin rights. You place it on your PATH yourself (~/.local/bin, for example) and run it. The amenbo command comes from the CLI installer.
• An older .deb / .rpm has to be removed by hand — the per-user build cannot remove it. sudo apt remove amenbo on Debian/Ubuntu, otherwise dpkg -r amenbo / rpm -e amenbo.
• The update prompt points at the AppImage — it used to look for the .deb, so on Linux “open the latest installer” did nothing.

Dates are judged by the day you are actually in

• --due tomorrow means the day after the day you typed it — it used to count from the UTC calendar day, so typing it before 9 in the morning in Japan saved a date one day earlier than asked. The same goes for today / +3d, for the overdue/today judgement, and for a start day’s arrival.
• Filtering by “today” no longer drops what you entered in the morning — --since today and decided_after:today were also cut on the UTC day, so a decision accepted between midnight and 9am fell out of “today” and the newest rows dropped off the activity list.

A setting changed from outside now reaches the open window

When a setting was rewritten from the CLI, a GUI left open kept showing the old value. It now updates in place.

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.