Hollow Code

Understand code, plan changes and review local edits with Hollow in your editor. Chat in the sidebar or open a wider editor tab, and add the files you want Hollow to see.

Preview: Hollow Code requires a Hollow account and an internet connection. Local and Cloud have different setup requirements and limits, explained below.

What you can do

• Ask about your code. Understand a project, investigate errors or review changes.
• Add context. Attach files, selected code, problems or available terminal output. Type @ to choose a workspace file or folder.
• Plan before making changes. Explore an approach in Plan mode, then choose Ask first or Review for coding work.
• Review local edits. Hollow asks before local file changes and shows edits in the editor's diff view.
• Run local commands with your approval. Local file changes and commands require the setup below.
• Return to your conversations. Find earlier sessions, queue a follow-up while Hollow is working, or continue from the editor view in Hollow Studio.

Get started

1. Install Hollow Code in VS Code 1.93 or later, or a compatible VSCodium or Theia IDE release, and open your project folder.
2. Run Hollow Code: Sign In from the Command Palette and approve the code in your browser.
3. Select the Hollow ghost in the Activity Bar and start a conversation.
4. Use Sessions to find earlier conversations or Open in Editor for more room.

Work locally

Chat is available in Restricted Mode. Local sessions use your open folders; file changes, commands and Studio session hosting require a trusted workspace.

By default, Local sessions can read files but cannot change files or run commands unless the Hollow bridge is running for that folder. The bridge is a separate preview tool that runs file work and commands in its sandbox. It requires a single open folder and its own approval to trust that folder. Run Hollow Code: Ask the Bridge to Trust This Workspace if needed. Hollow Code shows the command to start an installed bridge; contact us below for availability and setup.

Work in the cloud

Choose Cloud in the composer to work with a GitHub repository linked to a Space in Hollow Studio. You can select up to four repositories for a conversation. Cloud work can continue after you close your editor.

Cloud supports reading files, staging edits and read-only commands. It cannot install dependencies, run tests or scripts, start development servers, or provide an interactive terminal or live preview. Use Local for project commands.

Permissions and your data

Ask first and Review control when Hollow requests approval. Sessions started in your editor use its diff view for local file changes. Saved permissions can affect server approval prompts. Run Hollow Code: Manage Saved Permissions to inspect or remove them.

Local describes where file work and commands run. AI requests still use Hollow's online services. Your prompts, attached context and the file content needed for a task are sent to those services. Conversations and run history are stored on your Hollow account. Your sign-in key is kept in the editor's secure secret storage. The extension also sends activation and sign-in/sign-out events to Hollow. Read the Hollow privacy policy for more about data handling.

Help and feedback

Run Hollow Code: Show Logs for sign-in, connection or session errors. For account questions, setup help or feedback, visit Hollow contact.