Grux AI Download

Undo its shell. No account. Read its log.

An AI agent that can run entirely on your Mac, on Grux Local, a model trained for the jobs Grux gives it. Before any command that looks destructive, its shell takes a snapshot so undo can put your files back, and every command its shell runs goes in a plain text log. On Grux Local there is no API key at all, and there is never a Grux account or a Grux server.

Check each one: the snapshot, no account, the log, and what first run does.

Free, MIT licensed|macOS 14 or later, Apple silicon|Notarized by Apple|Drag it into Applications

On a fresh install one request leaves on its own: once a day Grux asks GitHub's public release page whether a newer version is out. Like any web request it names your Grux and macOS versions. Settings, General turns it off.

Star the repository on GitHub, and watch its releases to hear about new versions.

The 3.2 launch film, 54 seconds, with sound. What changed is just below.

What it does

Four promises, each one you can check.

It does the work.

It reads the window you are in, so you never paste a screenshot, and it runs commands in the folders you chose. 119 tools sit behind one Command Panel.

119 tools, 37 features, one Command Panelcounted from the app's own feature registry, 3.3.1

You can take it back.

Its shell snapshots your project before any command that looks destructive, into a separate shadow repository, so undo restores your files and your own commits stay where you left them.

before destructive cmd #1: find . -name loop-a23b-marker.txt -deletea real snapshot on our test Mac, Sep 27, 5:43 PM

You can read what it did.

Every command its shell runs and every file its file tool reads, refusals included, goes in a plain text log on your Mac. In the default guarded mode a push, deploy, publish or sudo waits for your tap.

"outcome":"blocked","path":"touch proof.txt","reason":"strict mode: 'touch' not on allowlist"a real line from the log on our test Mac, Oct 23, 9:27 AM

It can run on your Mac alone.

Grux Local is a model trained for Grux's jobs. It runs through Ollama with no API key, and nobody sees what you ask.

454 of 464 right after training396 of 464 beforeGrux Local 4B on a 16 GB Mac mini, 464 held-out Grux tasks

What to ask it

It suggests from what is on your Mac.

No stock prompts. Grux reads its own log, its snapshots and what you have connected, and offers only the asks that can work right now. The undo and log suggestions need a cloud model; on Grux Local it offers setup steps instead, because a small local model does not use those tools reliably yet.

Our test Mac, Sep 27, on a cloud model

Undo sort -o loop-a23b-sorted.txt loop… from 5:43 PMa snapshot of the session folder was taken right before it ranWhy did you refuse touch proof.txt?the log has the refusal at 7:51 PM: strict mode: touch is not on the allowlistWhat did you run today? (361 commands)every one is in the plain text log

Our test Mac, Oct 23, on a cloud model

Why did you refuse touch proof.txt?the log has the refusal at 9:27 AM: strict mode: touch is not on the allowlistWhat did you run today? (145 commands)every one is in the plain text logSet up Grux Local 4B for this Mac's 16 GBno local model yet, and the 4B is the size for Macs with 16 GB and up

Our test Mac, Nov 1, a quiet day, on a cloud model

Why did you refuse ~/Desktop/Grux?the log has the refusal at 11:29 AM: that folder is outside the allowlistSet up Grux Local 4B for this Mac's 16 GBno local model yet, and the 4B is the size for Macs with 16 GB and upLet Grux see the window I am inScreen Recording unlocks asks about whatever is on screen

A fresh 48 GB MacBook, any model

Set up Grux Local 9B for this Mac's 48 GBno local model yet, and the 9B is the size for Macs with 24 GB and upLet Grux see the window I am inScreen Recording unlocks asks about whatever is on screenConnect my calendaryour next meeting becomes something to prep for

The Command Panel

One panel. Everything else is a pane beside it.

Now

What needs you, in one list. A feature still waiting on something names the one thing it is missing, a mail server or a key, and nothing there is required to use the rest of Grux.

Optimize Grux

Four doors. Tune it: how sure it must be, how often it interrupts, what it spends and remembers. Change it: say what you want different, and Grux writes a work order your coding agent builds. Hand it over: your settings, theme and macros as a bundle. Let it improve itself: it proposes its own upgrades, and you choose how far that goes.

The Grux AI Command Panel on a Mac that has just installed it. The orb and the Grux AI wordmark, then one input reading: Type it, or turn listening on. Under NOW: Set up Mailbox, mail server. Set up Calendar, calendar. Then the Optimize Grux row. Under RECENT, one Chat. At the foot: Needs screen access, Grant, Listening off.

What is still being built sits behind the Labs door, badged once. Some of it is tooling built to run DotcomJack's own products: Jax Command, Jax HQ, Meta Ads, Social, Feature Review, Self-Upgrade and Workflows. It ships because deleting it would misrepresent what you are downloading, not because you will ever open it.

Every feature, one line each, generated from the app's own feature registry. Or read the answers: what Grux is, a local AI assistant for macOS, which LLM your Mac can run, meeting notes without uploading audio, shell commands, safely, your mail and calendar, every permission it asks for, keeping secrets out of a prompt, free with no account, driving it from the terminal, open source AI agents for macOS, open source ChatGPT alternatives, Mac apps that use Ollama and changing it with Claude Code. New: Grux Local, a local model trained for Grux. Also: what changed in 3.0, and after it, Grux vs Raycast AI, LM Studio, the Claude app and the ChatGPT app.

Local models

It reads this Mac and tells you what will run on it.

Point it at Ollama and the model for chat, naming and the background jobs runs on this Mac; Focus log, when on, still asks Claude. Mail and calendar still come from your own accounts, and Research still searches the web with your key. Local Models reads your actual hardware, budgets your actual memory, and rates each model against it before you download 17 GB to find out.

On the M4 Pro below: 48 GB of memory, 37 GB of it available to a model, Qwen 3 Coder 30B a good fit at 19.0 GB on disk, Qwen 3.5 35B marked tight at 24.0 GB, and one recommendation instead of a list. It will tell you what not to bother with.

The Local Models tab in Grux reading the Mac it is installed on: Apple M4 Pro, 48 GB of RAM, a 37 GB GPU and model budget, 14 cores, unified memory, rated 64 GB class. One recommendation: Qwen 3 Coder 30B. Below it, Qwen 3 Coder 30B a good fit at 19.0 GB on disk, Qwen 3.8 27B a good fit at 18.0 GB, Gemma 4 26B a good fit at 18.0 GB, Mistral Small 3.2 24B a good fit at 15.0 GB, GPT-OSS 20B a good fit at 14.0 GB, and Qwen 3.5 35B marked tight at 24.0 GB. The Ollama server is shown running externally at /opt/homebrew/bin/ollama with auto-serve off.

What it costs

$0

There is no hosted anything to pay for, no account to make and no subscription. You pay your model provider directly, on your own account, at their prices. Grux never sits between you and the bill, because nothing is proxied through any server we run. Run a local model instead and the running cost is $0 as well.

Chat needs one model, an Anthropic key, Ollama or an OpenAI-compatible endpoint, and nothing else. Research also wants a Brave Search key, Mailbox wants your IMAP details, Compare wants Ollama running. The Now list names what a feature still needs, and a feature you never open never asks you for anything.

Approvals

It stops and asks.

Grux can run a shell command, which is the feature most likely to end badly, so it is the one with the most in front of it. Commands run against a denylist, inside folders you chose. From chat, every shell command waits in Approvals until you press the button, and in guarded mode a push, a deploy, a publish or sudo does not run until you approve it.

The model's only route to your disk is one Swift file. It reads at most 1 MB of a file, gets 10 calls a minute across reading and listing combined, and cannot touch .ssh, .aws, .gnupg, your Keychains, your Mail, your Messages or your browser profiles at all. Out of the box the folder it may read is empty, because you have not picked one yet.

Every attempt is one line in a plain text log on your own disk, refusals included:

{"ts":"2026-08-25T14:02:11Z","tool":"fs_read",
 "path":"~/.ssh/id_ed25519","outcome":"denied_denylist","bytes":0}

Permissions

Nine, and only five are ever required by anything.

Each is asked for the first time you open the feature that needs it, and refusing one disables that feature and nothing else.

PermissionRequired byWhat saying no costs you
MicrophoneMeetingsTalking to Chat instead of typing
System audioMeetingsThe other side of the call
Screen recordingFocus logScreen context inside a chat turn
CalendarCalendarThe agenda block on Today
ContactsContactsResolving a name in Chat
AutomationNothingGrux driving your other apps
AccessibilityNothingKnowing what you have highlighted
NotificationsNothingBeing interrupted when a schedule fires
Full disk accessNothing, anywhereOne Labs feature, and only that one

One thing not to oversell. All nine are declared and shown to you during setup, but Grux does not yet check every one immediately before the system call that needs it. macOS still enforces it either way. What you may get is nothing back, rather than Grux explaining which permission was missing.

It is also not sandboxed, and the reason is boring: screen capture, AppleEvents and cross-app microphone access do not exist inside the App Sandbox. So the boundary is the Swift file above rather than the operating system, and your keys sit in the macOS Keychain and go to the provider they belong to. The app says that in its own interface, not just here.

The Integrations tab in Grux. Its own description reads: connect Grux to the services you already use, tokens are stored in your macOS Keychain, nothing is sent to a server, Grux talks to Slack and Notion directly from your Mac. Slack and Notion are both shown not connected, with empty token fields. Below them an Outbound webhooks section, empty, stating that Grux POSTs a JSON envelope signed with HMAC-SHA256 to each URL and that secrets are stored in the macOS Keychain.

Guardrails

The security layer is a separate package the app runs on.

The two jobs most likely to hurt you, keeping a credential out of a prompt and stopping the agent following a hostile link, live in their own Swift package: 125 tests, zero dependencies, MIT. Grux depends on it rather than carrying a copy, and Package.resolved shows you that rather than asking you to take our word for it.

It carries six published GitHub advisories against its own earlier releases, two critical, because six of the first nine tags failed to redact something. The tags stay resolvable, so anyone pinned to one gets told. That record is the reason to trust this one, and you can count them yourself: the advisories, the package.

Who builds Grux

A DotcomJack project, built in Detroit.

DotcomJack has been building and shipping its own products since 2015, about a dozen of them today.

That is why Grux exists. Running them was never bottlenecked on code. It was the hour a day spent moving between a mail client, a calendar, a terminal and four chat tabs that could not see any of it. Grux is the assistant built for that work: one that reads the window you are already in, handles the mail, and takes the meeting notes.

Grux has no account and nothing to buy. It is open source because it became useful enough to be worth other people's time, and because software that reads your screen and your mail should be readable back.

What is not finished sits behind the Labs door and says so. If something breaks, open an issue and tell us what you were doing.

Get it

Free, and the source is right there.

Bring an Anthropic key or any OpenAI-compatible endpoint, or point it at Ollama and pay nobody at all. The licence text is in the app bundle.

And star it on GitHub. There is no account to make, no email to hand over and nothing to buy, so a star is how other people find out Grux exists.

Requires
macOS 14 or later, Apple silicon
Signing
Developer ID, notarized by Apple and stapled, so it opens without a right click
Licence
MIT licensed, and the whole tree is public
Model
Your own Anthropic key, any OpenAI-compatible endpoint, or Ollama running locally and no key at all

There is no installer, and nothing installs itself: once a day Grux asks GitHub's public release page whether a newer version exists, sending no account or install id, though like any web request it carries your IP address and your Grux and macOS versions, and only tells you (Settings, General turns it off). Open the DMG, drag Grux to Applications, and open it. To check what you got before you run it: spctl -a -vv /Applications/Grux.app should say accepted, and name Notarized Developer ID as the source.