Skip to content

engRAM 1.12.0 - a menu bar app for the Mac

Choose a tag to compare

View all tags
@MaxFreedomPollard MaxFreedomPollard released this 26 Jul 04:13
v1.12.0
b4fa740

engRAM had no face. Whether memory was open, what it had learned, and the settings worth changing all lived behind a terminal.

engram menubar

pip install 'engram-memory-vault[menubar]'
engram menubar

Click the status bar icon and a popover shows:

  • State - locked or unlocked, how many memories, how many you actually stored (as opposed to seeded starter facts).
  • Three settings - the capture hook that saves memories Claude Code writes; whether the built-in starter facts join your searches; and auto-lock (15 / 30 / 60 min / Never).
  • The last five memories - text, timestamp, and tags, newest first.

No dock icon, no window to manage.

How it is built

  • It holds no vault. State comes from shelling out to the CLI, so an idle status bar app is not sitting on a 300 MB embedding model.
  • The toggles work while locked. Settings live in <vault>.config.json, which contains no secrets, so changing a preference never demands a passphrase.
  • PyObjC is optional. It is macOS-only and irrelevant to the CLI and MCP server, so it ships as the [menubar] extra and the default install is unchanged everywhere else.
  • The data layer is tested on every OS. AppKit is imported inside run(), never at module scope, so everything the popover displays and every setting it writes is covered by CI on Linux and Windows as well as macOS.
  • engram menubar --render out.png draws the popover to a file and exits. Photographing a live status bar window needs screen-recording permission, and a UI nobody can look at in an automated check is a UI that rots. --self-check prints the same state as text.

155 tests green.

Assets 2
Loading