Skip to content
↳ LoopCodeby Heksync

KEEP THE CONVERSATION NEXT TO THE CODE

Your AI coding agent, inside VS Code.

The LoopCode extension places the agent in the editor you already use. Open a trusted project folder, sign in, and ask it to explain, fix, or build something. It reads and changes files in that workspace and shows the commands and output needed to check the result.

By Heksync product team · Reviewed

Install and open the extension

  1. Install heksync.loopcode from the Visual Studio Marketplace, or use the VSIX linked on the download page.
  2. Open a project folder in VS Code 1.95 or newer. LoopCode stays off in Restricted Mode.
  3. Open the LoopCode activity-bar icon, or use Command–Escape on macOS and Ctrl+Escape on Windows or Linux.
  4. Sign in through the browser and approve the code shown by the extension. CLI sign-in is shared where the credential store is available.
LoopCode on the Visual Studio MarketplaceExtension download and VSIX fallback

Add exactly the code you mean

Select a block and use Add Selection to LoopCode from the context menu. The shortcut is Command–Option–K on macOS or Ctrl+Alt+K on Windows and Linux. Explain the behavior you expect alongside the selection; a highlighted implementation alone does not define the requirement.

File paths in answers open in the editor. Read the changed files and diff, then inspect the test or command output. You can start a new conversation, open it in another tab, or return to a previous conversation for the same folder.

Example request after selecting a handler
This handler accepts negative quantities. Trace its callers,
add validation at the boundary, and add a regression test.
Keep the success response compatible with existing clients.

Remote work runs where the code is

Remote SSH, WSL, Dev Containers, and Codespaces are supported by the extension. In these environments, the engine runs in the workspace environment rather than treating your local desktop as the project. Install the extension in the appropriate remote extension host and confirm that project dependencies and test commands exist there.

A remote editor session does not imply access to the desktop app's integrated browser. Plan verification around the tools available in that environment.

Account, permissions, and privacy

Desktop, CLI, and VS Code share plan usage. Choose whether to ask about edits or permit workspace edits automatically, and use Plan mode for an approach you want to review first. Inspect command requests and the final patch before accepting work.

Project files stay in the workspace environment, and extension conversations are stored locally in ~/.loopcode/vscode there. Prompts and relevant code context are sent for hosted inference; this is not a promise of offline processing.

Platform and account setupHeksync privacy policy

KEEP GOING

A useful next step.

An AI coding assistant, with a path to action.LSP code intelligence for your coding agent.An AI coding agent for your terminal.

Put it to work in your project.

Desktop, CLI, and VS Code. One LoopCode account. Free to start.

Get LoopCode