Notifications
Four channels, all off until you turn them on, and a promise that you will not be nagged.
Everything is off until you say otherwise
No channel is on by default. Email in particular is opt-in and stays that way — nothing marketing-shaped is ever sent to an address that did not ask for it. Receipts, refunds and verification codes are not affected by any of this: a receipt is not a preference, so it arrives whatever your settings say.
The four channels
•
Web — notifications from localkeep.ai in your browser. Needs the browser's permission first.
•
Desktop — native notifications from the macOS and Windows apps.
•
Mobile push — the iPhone and Android apps, delivered through Firebase Cloud Messaging.
•
Email — a monthly newsletter and occasional product news. Off unless you turn it on.
Being asked
Once you have been using the product for a little while, you may see a small card offering to turn notifications on. It is deliberately not a permission dialog on page load: a browser grants permission only once per site, so firing that prompt before you know what it is for spends the single attempt for nothing. The card explains first, and only asks the browser when you press the button.
•
You will be asked at most twice, ever, and never twice within a month.
•
"No thanks" is permanent. It is not a snooze, and the card does not come back.
•
If you already granted permission, the setting simply switches on — you are not asked a question you have answered.
•
Turning notifications on never turns email on. Email is only ever the switch in Account.
Changing your mind
Account → Notifications has a switch per channel, and they work in both directions at any time. If your browser is blocking notifications for localkeep.ai, the web and desktop switches cannot take effect and the page says so — that one has to be changed in your browser's own site settings, usually from the icon at the left of the address bar. Nothing this app does can undo a block you gave the browser.
When we contact you about being away
If an account goes quiet, you may get a single reminder after a week and, if it stays quiet, one more after a month. There is a lifetime cap of two of those win-back messages and never more than one in any thirty-day window — ignoring two is an answer, and continuing past it is how a product becomes spam. Using the product at all resets the clock, and every one of these respects the channel settings above.
What you get told about
•
Long runs and automations finishing, so you do not have to watch a tab.
•
Model downloads completing.
•
Anything that needs a decision from you before it can continue.
•
Billing events that require action, which are sent regardless of the marketing opt-in.
Last updated: 26 August 2026
All documentation
Installation
Install the CLI on macOS, Linux or Windows, and sign in.
Setup, start to finish
The whole path on one page: install, sign in, pick local or hosted, get an answer.
Connecting accounts
One account everywhere, registering devices for the SMS bridge, and OAuth integrations.
Models
Pull open-weight models, switch between them, and run fully local.
Using models on every client
What runs locally in a terminal, a browser tab, a phone and the desktop app.
Commands
Every terminal command and every slash command, each with its own page.
Editor integrations
VS Code, Cursor, JetBrains, Neovim, Sublime, Zed, Godot, Unity, gh and git hooks.
The SMS bridge
Send a task to your own machine from your phone, and get the answer back.
The apps
One React Native codebase behind iPhone, Android, web and desktop — and how to run it.
Automation Studio
Idea to production: flows, per-step models, your machines or ours, live editing.
Enterprise seats
Licensed team seats under one owner account — invites, billing, and how seats resolve.
API reference
API keys, authentication, chat completions, pricing and errors — for your own software.
Privacy
What leaves your machine, what never does, and how anonymisation works.
Troubleshooting
When a model will not load, a command hangs, or the CLI cannot be found.