Editor integrations
12 integrations, all of which drive the same lk CLI. Each has its own page with install steps, keybindings and the things that catch people out.
The CLI in depth
2:22
Every integration is a front end over this. What you see here is what all ten are doing underneath.
Every integration is a thin front end over the lk command. That means one place to configure things, one place to update, and identical behaviour whichever editor you are in.
Install the CLI first
None of them bundle the CLI. Without it, the integration installs cleanly and then does nothing at all — which looks like a broken extension rather than a missing dependency.
•
pip install local-keep-ai-cli
•
lk login
Editors and IDEs
VS Code
A sidebar chat, inline edits on the current selection, and a command palette entry for every lk command.
Cursor
The same extension as VS Code, installed from the registry Cursor actually reads.
JetBrains IDEs
A tool window and editor actions across IntelliJ, PyCharm, GoLand, WebStorm, CLion, RubyMine, PhpStorm, Rider and Android Studio.
Eclipse
A chat view, plus explain and test-generation on the file in the active editor, from the menu bar or the editor's right-click menu.
Neovim
A floating chat window and :Lk commands, with no daemon to manage.
Sublime Text
A command-palette front end for the CLI, including the shell escape.
Zed
A context server for Zed's agent panel, so Zed's own agent can call into your local models.
Game engines
Godot 4
An editor dock and Tools-menu actions, aware of the current scene and script.
Unity Editor
An editor window that can read the open scene and the selected assets.
Unreal Engine
A dockable editor panel that answers from your own models, plus explain and test-generation on the file you have open.
Version control
GitHub CLI
Review a PR, summarise a diff, or draft a description without leaving the terminal.
Git hooks
Two optional hooks that write commit messages from the staged diff. No editor involved.
Where to install from
Prefer the registry listing over the GitHub repository wherever one exists. A marketplace install updates itself, is signed by the registry, and is what your editor's own extension browser expects. The repository is the fallback for when a listing is unavailable, and the place to read the source.
The downloads page lists all ten with both links side by side, registry first.
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.
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.