Loxie for VS Code
Chat with Loxie inside VS Code. Sidebar chat, inline completions, and
"ask about selection" - all billed to your Loxie plan. No API keys to copy,
no per-model billing to wire up.
Works in VS Code, Cursor, Windsurf, and VSCodium.
Features
- Sidebar chat +
@loxie participant with streaming Markdown, references, and conversation history
- Inline completions (FIM, ~120ms debounce) with language-aware stop tokens
- Inline edit (⌘K / Ctrl-K) - selection rewrite previewed as ghost-text, accept/reject inline
- Agent mode -
/agent produces a multi-file diff; staged in a side-bar TreeView, applied behind a single confirm
- Multi-model race - fan one prompt to up to 4 models in parallel, "Keep this" on the winner
- Hybrid RAG - lexical TF-IDF + semantic embeddings (cached locally, content-addressed)
- Test generation with a self-healing loop (vitest / jest / pytest /
go test)
- Notebook support - explain/fix/extend cells from the cell title bar,
@cell mention
- Quick fixes - every diagnostic offers "Fix inline with Loxie" alongside chat-based "Fix with Loxie"
- Rich
@-mentions - @file, @selection, @problems, @terminal, @git, @diff, @pr, @docs, @url, @symbol, @cell, @mcp
- Native Accounts integration - Loxie sessions live in VS Code's Accounts menu and are reusable by other extensions via
vscode.authentication.getSession("loxie", …)
- MCP - call any
.loxie/mcp.json tool from chat or via @mcp:server/tool
- Routing pill - every reply ends with model · time-to-first-token · cost
- Privacy-first - your code stays on your machine unless you explicitly send it
Install
From the Marketplace (recommended)
- Open the Extensions view in VS Code (
⇧⌘X / Ctrl+Shift+X)
- Search for Loxie
- Click Install
- Click the Loxie icon in the activity bar → Sign in with Loxie
From Open VSX (Cursor / Windsurf / VSCodium)
Search for Loxie in the Extensions view, or visit
open-vsx.org/extension/loxie/loxie.
From a .vsix file
Download the latest .vsix from loxie.co/app/extensions,
then run Extensions: Install from VSIX… from the command palette.
How sign-in works
Loxie uses a device-code flow: the extension opens
loxie.co/app/extensions/authorize in your browser, you approve once, and a
scoped session token is returned and stored in VS Code's SecretStorage. The
token is sent as a bearer to the Loxie backend, which validates the request,
meters usage against your plan, and persists chat history under a per-user
VS Code conversation visible from your Loxie dashboard.
Sign out anytime: command palette → Loxie: Sign out.
Settings
| Setting |
Default |
Description |
loxie.model |
auto |
Default chat model. auto uses Loxie's smart routing. |
loxie.completions.enabled |
true |
Toggle inline code completions. |
loxie.apiBase |
Loxie backend |
Override only if you self-host Loxie. |
Commands
| Command |
Default keybinding |
Loxie: Sign in |
- |
Loxie: Sign out |
- |
Loxie: New chat |
- |
Loxie: Ask about selection |
⌘/Ctrl+Alt+L |
Privacy
- The extension never reads your workspace files unless you explicitly trigger
a command (e.g. Ask about selection) or request completions
- Inline-completion context is a small window around your cursor (≤ 2 000 chars
prefix, ≤ 800 chars suffix); files at rest are never uploaded
- No telemetry. Usage events are limited to what the Loxie backend records for
billing, identical to web and Chrome-extension usage
- Session tokens live in VS Code's encrypted
SecretStorage
Support
License
MIT - see LICENSE.
| |
