Installation
Get the x64 Setup for Windows or universal DMG for macOS from the download page, then follow the standard installation flow for your system.
Resources / Documentation
Installation, working modes, tool permissions, model selection, project indexing, Remote SSH, account management, and troubleshooting in one place.
This guide reflects LukAi desktop 2.1.2 and the current LukAi Mobile experience.
Getting started
The behaviors below are directly visible in LukAi desktop 2.1.2.
StableGet the x64 Setup for Windows or universal DMG for macOS from the download page, then follow the standard installation flow for your system.
LukAi creates a short device code. Sign in on the browser device page and approve it; your account password is not passed to the desktop application.
Open a local folder, multi-folder workspace, or Remote SSH target. Explorer, terminal, Git, and debugging retain standard IDE behavior.
Check for updates from the account center. The interface shows Downloading while retrieving a package and Applying during installation.
Agent workflows
The behaviors below are directly visible in LukAi desktop 2.1.2.
StableDescribe a task in natural language. The agent can read, search, and edit project files, run terminal commands and tests, and show tool steps live in the conversation.
LukAi studies the workspace before writing code and produces an actionable plan. Apply plan adds a visible user command, switches to Build, and begins implementation.
Substantial work is separated into requirements.md, design.md, and tasks.md. Each document is approved separately before implementation starts in the same conversation.
For an important ambiguity, the agent can ask one to three questions. Choose an option or enter a short answer and continue the same task without losing context.
Conversation and context
The behaviors below are directly visible in LukAi desktop 2.1.2.
StableUse Ctrl/Cmd+L to attach the open file or selected code. Files, folders, code selections, and images remain removable context items until the message is sent.
Return to recent threads from the searchable header selector, open a new conversation, duplicate the current thread, or delete it. The selector stays hidden before a real message exists.
While the agent works, Add to queue prepares the next turn without interrupting the response. Send now stops the active response and starts the new message. Invalid choices are hidden.
LukAi automatically summarizes older working context while preserving the complete transcript, checkpoints, and file history. Run /compact manually with an optional focus when needed.
Models and reasoning
The behaviors below are directly visible in LukAi desktop 2.1.2.
StableThe model list comes from the gateway. Account, group, quota, and provider capacity can change which models are selectable.
Premium models receive animated text treatment. Quota policy, exhausted state, and full-capacity information appear on the selection row.
Each model's credit multiplier is visible in the list. Because policy can change it, one credit is not treated as one fixed request.
Choose minimal, low, medium, high, or very high effort. Chat, Quick Edit, Autocomplete, Apply, and SCM can share a model or use separate assignments.
Code intelligence
The behaviors below are directly visible in LukAi desktop 2.1.2.
StableAfter sign-in, the project is indexed in the background. File changes update incrementally instead of triggering a full scan, and generated or dependency folders are excluded.
The agent can use file paths, the project tree, text or regex search, and semantic search. Settings show index state, chunk count, and partial or failed status.
Repeated full-index requests are coalesced and automatic retries have a five-minute cooldown. Normal incremental updates continue during that period.
Ctrl/Cmd+K applies a targeted edit to selected code. Optional FIM inline completion can be enabled in settings and assigned a separate model.
Approvals and revert
The behaviors below are directly visible in LukAi desktop 2.1.2.
StableFile edits, terminal commands, and MCP tools have separate automatic approval controls. With automatic approval off, the agent waits for an explicit accept or reject decision.
Inspect changed files and lines in a live diff, then accept or reject one file or all changes together.
A bounded checkpoint and changed-file summary are retained for a completed agent turn. Incomplete or unsafe-to-match turns are not presented as reversible.
If a file changed again after the agent turn, LukAi does not silently overwrite it. Conflict checks determine whether a safe revert is possible.
Terminal and web tools
The behaviors below are directly visible in LukAi desktop 2.1.2.
StableThe agent runs a command in the terminal and reads its exit code and output. When terminal approval is enabled, it shows the operation summary first.
Start a development server or watcher in a separate terminal, send additional input, and stop it when the task is complete.
Fetch the text of a URL or open it in the system browser. Network-dependent steps remain visible in the tool flow.
Collect HTTP status, redirects, console and page errors, failed requests, and screenshot results.
MCP and Skills
The behaviors below are directly visible in LukAi desktop 2.1.2.
StableList and use tools from configured MCP servers during a task, with an approval policy separate from files and terminal commands.
Open the MCP configuration from LukAi settings, enable or disable a server, and inspect the available tools.
View, create, edit, disable, or delete Agentskills.io-compatible packages. The agent loads relevant skill content during a task.
Import a Skill package from a GitHub repository or local folder, and review its source and permissions before use.
Remote SSH
The behaviors below are directly visible in LukAi desktop 2.1.2.
StableManage profiles from ~/.ssh/config or a selected custom config file through SSH Targets in Remote Explorer.
Open a target in a new or existing window and return quickly to previously used remote folders.
SSH keys, ssh-agent, passwords, ProxyJump, and OpenSSH settings are used on the desktop. Private keys and config bodies are not sent to the gateway.
Select Linux, macOS, or Windows as the SSH target platform. Files, terminal operations, and the agent run against the remote workspace.
Account, updates, and support
The behaviors below are directly visible in LukAi desktop 2.1.2.
StablePlan, period credits, reset date, token information, updates, and support actions appear in one focused surface.
Use multiple windows on one computer. To move to another computer, explicitly take over the session; active agent work on the previous computer is stopped.
The gateway can require a minimum client version for security or compatibility. An older client cannot send model requests until it is updated.
Run LukAi: Send Diagnostic Information (Support) from the Command Palette. It creates a shareable DX code; including the active conversation requires separate approval by default.
Mobile companion
The behaviors below are directly visible in LukAi desktop 2.1.2.
ReadySee online desktop IDE and workspace sessions for the same account. The mobile application does not compile desktop files by itself.
Remotely manage conversations, models, Build/Plan, Spec, queueing, stopping, tool approvals, clarification answers, and safe revert.
See saved desktop SSH profile names and ask LukAi to open the selected profile in a new Remote SSH window. SSH secrets remain on the desktop.
Push notifications and diff review are active. LukAi Mobile is currently available to a limited number of users. The mobile application is not a full code editor.
LukAi 2.1.2
Download the current desktop package and complete your first device sign-in.