LoopCodeUse LoopCode
VS Code extension
Use LoopCode inside VS Code — the same agent as the desktop app and the CLI, in a panel beside your editor, with your selection and files as context.
Install
Install LoopCode (heksync.loopcode) from the Extensions view, or from the command line:
code --install-extension heksync.loopcode
It needs VS Code 1.95 or newer and a trusted workspace. Open the LoopCode icon in the activity bar, sign in through your browser, and start a conversation.
What you get
The extension runs the same engine as the desktop app and the CLI, in your window's folder, signed in with the same account and plan. Everything on How LoopCode works applies: the same tools, permission modes, proof of done, skills, MCP servers, hooks and settings files.
The panel has the desktop app's composer: @ mentions, attachments, the model and mode pickers, and editing a sent message to rewind and try again.
Commands
Open the Command Palette (⌘ ⇧ P) and type LoopCode:
| Command | Does |
|---|---|
| LoopCode: Open LoopCode | Show the LoopCode panel |
| LoopCode: New Conversation | Start a new conversation |
| LoopCode: Open in New Tab | Open LoopCode in an editor tab instead of the side panel |
| LoopCode: Add Selection to LoopCode | Put the selected code into your next message |
| LoopCode: Add File to LoopCode | Mention the current file |
| LoopCode: Settings | Open LoopCode's settings |
| LoopCode: Sign In / Sign Out | Your LoopCode account |
| LoopCode: Show Plan Usage | Your plan and its usage windows |
Keyboard shortcuts
| Action | macOS | Windows and Linux |
|---|---|---|
| Open LoopCode | ⌘ Esc | Ctrl Esc |
| Add selection to LoopCode | ⌘ ⌥ K | Ctrl Alt K |
Settings
| Setting | Default | Description |
|---|---|---|
loopcode.showEditorButton | true | Show the LoopCode button in the editor title bar |
Agent behaviour — permission rules, hooks, MCP servers, sandbox — is configured in LoopCode's settings files, shared with the desktop app and the CLI.
Remote workspaces
With Remote - SSH, WSL or Dev Containers, the extension runs where your code is: the engine works on the remote machine's files and runs commands there. Sign in once in that window.
Where conversations are kept
The extension's conversations are stored on the machine where the workspace lives, in ~/.loopcode/vscode.