If you are on v0.3.2, update. The browser editor in v0.3.2 opened as a blank page — this release fixes it.
The fix that matters
scripts/edit.sh and scripts/review.sh open your register as a form in your browser. In v0.3.2 that page rendered blank: an invisible full-screen panel sat on top of the form from the moment it loaded. Nothing was broken about your data, and the Terminal path was unaffected, but the terminal-free journey the release was named for did not work. Found by opening the page in a browser during the next piece of work; no automated test could see a covered page, so the suite now checks for it directly.
New: import from 1Password (optional)
If you keep your logins in 1Password, the editor can now seed your register from it. A Pull from 1Password button appears in the editor; it lists your vaults, then walks you through the accounts one at a time, money first — banks, cards and crypto before anything else — so stopping early still captures what matters. There is also an "add all as drafts" mode if you would rather triage afterwards.
It reads titles, categories and web addresses only. No password, one-time code or any other concealed field is ever requested, returned or stored, nothing is written to disk, and 1Password's own approval prompt gates every pull. The register has always held pointers to where a login lives, never the login itself, and that does not change. A test greps the whole codebase on every CI run to keep it that way.
Needs the 1Password CLI and 1Password 8 with CLI integration enabled. Without it the button explains itself and the manual path is untouched — the importer only ever saves you typing.
Also
- Sealing now saves what is on screen first, so anything added just before you seal is actually in the sealed file.
- The yearly review warns you if imported entries still carry the wording and action the importer guessed, rather than yours. It warns; it never blocks.
- Two same-titled items in your vault (two cards both called "Mastercard") are no longer treated as one. The editor asks for something that tells them apart, and next year's re-import offers the one you have not filed yet.
- Internal: the local editor server now serialises saves against sealing, so a save can never land inside a seal.
Nothing about the executor's recovery path has changed. It is still stock age and ssss, still 2-of-3, and any shares and printed instructions you already have remain valid.
Install
Download executor-file-v0.3.3.tar.gz below (not GitHub's "Source code" links). Verify it if you like:
shasum -a 256 -c executor-file-v0.3.3.tar.gz.sha256