Grux 1.2.1

Grux 1.2.1 for Apple silicon. Notarized and stapled by Apple, so it opens on a Mac that has never seen it.

Requires macOS 14 or later, Apple silicon. sha256 a711dfe417f1bac640eebf5f2032bcb456c47fd8bc9cce10601006eac8efc84c

What is new since the last public release

Grux has a command line. It can be set up and driven entirely from the terminal, without opening a window. The point is not that a terminal is faster. It is that the coding agent already sitting in that terminal can do the work with you: install Grux, wire it into the rest of your machine, and go on extending it long after setup is done. Every command runs unattended and every command can print itself as a prompt instead of running, so you can hand the job to whichever agent you already use. There is an MCP bridge for agents that speak it. Reads answer with Grux closed, writes go over a local Unix socket, and Grux still opens no network port.

A first launch is quiet now. Forty nine services start when Grux opens. Twenty five of them used to do something nobody had asked for: creating folders, reading a keychain, speaking out loud at seven in the morning on a Mac that had never been set up. Auditing the launch path afterwards found eight more. Nothing in that work is a feature. Every line of it is Grux doing less, or doing the same thing behind a switch you can find and that survives a restart.

Setup stops claiming things that are not true. The last day before this release was one repeated shape: a readiness check consulting a value that nothing updates. A key in the Keychain read as proof that setup had finished, so a reinstall dropped you into the app with permissions never asked for. The Automation screen read a value nothing in the app had ever written, so granting Automation could not satisfy it no matter what you did. A refusal from the model provider was waved through, so setup reported success and the first message failed. And the local path checked that a model server was running without checking it held the model being asked for.

All 41 of those readiness checks were audited afterwards. Exactly two are stored rather than read live, and both were among the broken ones. A test now asserts that a stored answer has something that writes it.

You do not need a key. Pick nothing during setup and Grux asks for nothing beyond a model to answer with, and that can be a local one with no key at all, once Ollama is installed. Grux fetches the model that fits your Mac; you supply the runtime. A key is worth adding when you have one, and Grux says so once rather than nagging.

Full detail in CHANGELOG.md.