lk automation cloud
Set YOUR cloud project for automation deploys — never the company's.
What it does
Set YOUR cloud project for automation deploys — never the company's.
The runner REFUSES every cloud deploy until this is set, and always refuses commands that touch Local Keep AI's own infrastructure. This is what keeps a build billed to YOU and off the company's account. Deploy commands must name this project explicitly (e.g. `--project <id>`) so they cannot fall back to the machine's ambient cloud login.
Usage
Run lk automation cloud from your terminal. Add --help to any command to see its full flag list, which is always authoritative over this page.
•
lk automation cloud
The CLI in depth
2:22
See automation cloud used in a real session, alongside the rest of the other commands.
Related commands
•
lk automation apple — Connect YOUR Apple App Store Connect API key so automation signs/uploads iOS + macOS builds with YOUR developer account.
•
lk automation disable — Stop this machine running Automation Studio commands.
•
lk automation enable — Allow Automation Studio's "Ship it" step to run commands here.
•
lk automation play — Connect YOUR Google Play service-account JSON so automation uploads Android builds to YOUR Play account.
•
lk automation run — Watch for Automation Studio steps aimed at this machine and run them.
•
lk automation status — Show whether this machine will run Automation Studio commands.
•
lk catalog — Browse the full Local Keep AI model catalogue, labelled for YOUR plan.
•
lk corpus build — Harvest the cwd into a training-corpus snapshot.
•
lk corpus pull — Download latest snapshot from GCS.
•
lk corpus push — Upload latest local snapshot to GCS.
•
lk daemon start — Start the remote-agent daemon: the message bridge, detached.
•
lk daemon status — Show daemon state — from the pid file plus a live process check.
Where this is defined
automation cloud is declared in ai-platform/sage/core/autonomous_helpers.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.