Lana Code for Visual Studio Code
Ask questions about your code, edit files, and run commands from the Secondary Side Bar. Lana Code includes its coding runtime and connects to your Lana account. Lana website
Get started
The first Marketplace pre-release supports Apple Silicon Macs running macOS 14.2 or later.
- Use Microsoft Visual Studio Code 1.106 or later; macOS requires 14.2 or later. Choose the build for your operating system and architecture when available. If you received a VSIX, choose Extensions: Install from VSIX… in the Command Palette.
- Open and trust a single local workspace folder. Choose Lana Code in the Secondary Side Bar or run Lana Code: Focus Chat from the Command Palette.
- Choose Continue with Google and finish Lana sign-in in your browser. Coding access and charges follow your Lana account’s plan and available credits. Run
/account or /usage to see your account and usage, or /billing to open Lana billing in your browser.
- Save your workspace files, enter a task, and press Enter to send. Use Shift+Enter for a new line.
Work with Lana
- Choose what to share. The composer can include an active file reference. Remove its chip to leave it out, or attach selected lines to send their text. Use +, type @ at the start of a word, or run Lana Code: Attach File to Chat to pick another workspace file. File chips send references. Lana can read saved files during a task when its permissions allow.
- Review commands and edits. Expand a command group to see the working directory, command, output, and exit status. Select a changed filename to compare before and after in the editor. When snapshots are unavailable, Lana shows the patch. Use VS Code Source Control to review changes made by shell commands as well.
- Stop or continue a chat. Stop interrupts an active turn. Open the chat-title menu to search and resume up to twelve previous chats in the same window. A chat whose runtime is unavailable opens as a read-only transcript. Resuming waits for your next message. Edit last request lets you review and resubmit a failed request when available.
Permissions and network access
New chats start in Auto. Use the permission selector or run /permissions to change the mode. Stop an active turn before changing modes.
| Mode |
How it works |
| Auto |
Runs routine workspace tasks and asks when a command requests extra access. |
| Ask every time |
Prompts you to review command and file-change requests that need approval. |
| Accept edits |
Applies permitted workspace edits and prompts for command approvals. |
| Plan |
Keeps the workspace read-only while Lana explores and proposes a plan. |
| Full access |
Requires confirmation and gives Lana the local user’s filesystem and network access. A resumed Full access chat starts in Auto. |
For scoped tool access, Ask shows an approval when the runtime provides a reviewable request for a new network host. Requests without a reviewable approval stay blocked. Switch to Block or remove remembered hosts in Chat settings. Lana still connects to its online service for sign-in, account information, and model requests.
Skills and MCP
Use + → Skills… or /skills to manage local skills and attach an enabled skill to your next message. Lana rechecks the selected skill when you send. Use + → Commands… or start a draft with / to find other commands. /workspace switches your Lana account workspace and starts a fresh chat in the open VS Code folder.
Use + → MCP servers… or /mcp to connect a server over HTTPS or loopback HTTP. You choose and confirm the endpoint. Manage connection checks, tool reloads, and OAuth or bearer authentication from the server’s settings. Saved bearer tokens use VS Code SecretStorage. The operating system keyring can retain an OAuth sign-in after you remove a server. Revoke that access through the provider.
In Auto, Ask every time, and Accept edits, Lana shows the MCP server and reported arguments for tool approval. Full access can run MCP tools without a per-call prompt. Plan and network Block pause MCP connections, including connection checks and OAuth sign-in.
Privacy and data flow
Lana’s online service processes your requests and the context needed to answer them. Context can include your messages, attached selections, file paths and excerpts, tool results, and command output. When you use an MCP server, Lana sends tool requests and their arguments to the server you configured.
Lana keeps its sign-in session and local runtime conversation files in VS Code’s extension storage. Chat history is scoped to the current window. Signing out, changing workspace or Lana account, or reloading the extension clears that window’s history. Review the context chips and tool requests before sharing sensitive information.
