lk sms allow-firewall
Open Windows Firewall on TCP+UDP 1716 so KDE Connect inbound works.
What it does
Open Windows Firewall on TCP+UDP 1716 so KDE Connect inbound works.
Adds two inbound allow rules to Windows Defender Firewall: • TCP 1716 — phone reconnects to Local Keep AI • UDP 1716 — phone discovery broadcasts reach Local Keep AI Requires elevation (UAC prompt). On macOS / Linux this is a no-op since neither blocks 1716 by default for the user's listening process. Without these rules, kdeconnectd's own firewall exception covers only `kdeconnectd.exe`, NOT the Python process that takes over the port — so Local Keep AI binds 1716 successfully but the phone's traffic never reaches it.
Usage
Run lk sms allow-firewall from your terminal. Add --help to any command to see its full flag list, which is always authoritative over this page.
•
lk sms allow-firewall
On your phone
0:41
See sms allow-firewall used in a real session, alongside the rest of the sms commands.
Related commands
•
lk sms contacts add — Add an authorized contact — accepts email addresses or phone numbers.
•
lk sms contacts clear — Remove ALL authorized contacts from this account.
•
lk sms contacts list — List all phone contacts authorized to send commands to your Local Keep AI computers.
•
lk sms contacts remove — Remove an authorized contact — they will no longer be able to control Local Keep AI.
•
lk sms devices — List all computers registered to your Local Keep AI account.
•
lk sms diagnose — Run health checks across the bridge — auth, WS, contacts, native delivery paths.
•
lk sms kde-takeover — Replace the OS KDE Connect daemon with Local Keep AI's parallel listener.
•
lk sms logs — Tail the bridge log file (live output — Ctrl-C to stop). `--no-follow` exists because following is useless to a script.
•
lk sms restart — Restart the local SMS bridge daemon.
•
lk sms setup — Guided setup — bridge email, computer name, authorized phone contacts.
•
lk sms start — Start the bridge daemon in the background — requires lk login.
•
lk sms status — Show this computer's bridge status and your account-wide devices/contacts.
Where this is defined
sms allow-firewall is declared in ai-platform/sage/commands_sms.py. This page is generated from that source, so it cannot describe behaviour the CLI does not have.
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.
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.
Notifications
Four channels, all opt-in, how to change them, and the limits on re-engagement.
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.