VS Code

The Hull Code extension brings Hull's agents into VS Code. It also works in editors built on VS Code, such as Cursor and Windsurf. The extension includes its own copy of the Hull runtime, so you don't need to install the Hull CLI.

InstallCopy Anchor Link

code --install-extension hullcode.hull-code

After installing, open Hull Code from the activity bar, then sign in or connect a provider under Settings > Providers.

What you can doCopy Anchor Link

• Chat with agents in the sidebar. Switch between the code, plan, ask and debug agents, or your own custom agents. Press Cmd+. (macOS) or Ctrl+. to cycle agents.
• Open a chat in its own tab with Hull Code: Open in Tab.
• Run agents in parallel with Agent Manager (Cmd+Shift+M or Ctrl+Shift+M).
• Act on code from the editor. Select code, right-click and open the Hull Code submenu to explain, fix or improve it, or add it to context.
• Work with the terminal. Right-click in the terminal to add output to context, or ask Hull to explain or fix a command. Press Cmd+Shift+G (macOS) or Ctrl+Shift+G to generate a terminal command.
• Generate commit messages from the Source Control view.
• Get inline suggestions with autocomplete.
• Review changes with Show Changes and the /review command.
• Extend Hull with skills, commands, subagents and MCP servers.

Keyboard shortcutsCopy Anchor Link

Settings and config filesCopy Anchor Link

Most agent settings, such as models, agents, permissions, MCP servers and instructions, live in Hull's config files rather than VS Code settings. The extension's Settings screen edits these files for you:

The Hull CLI, Hull Desktop and the JetBrains plugin read the same files, so your setup carries across. After editing a file by hand, run Hull Code: Reload Config and Skills from the Command Palette. See Settings for the full list of keys.

A few options are VS Code settings under hull-code.new.*. The most useful ones:

Proxy and certificate settingsCopy Anchor Link

The extension starts its Hull runtime with VS Code's network settings. On a managed network, set up the proxy and certificates in VS Code rather than in a separate CLI install.

• Set http.proxy to your organization's proxy URL.
• Use http.noProxy for hosts that should bypass the proxy.
• Leave http.proxySupport on unless you want VS Code and Hull Code to ignore proxy settings.
• If your network inspects HTTPS traffic, install your organization's root certificate in the operating system's trust store.
• If that isn't enough, set hull-code.new.extraCaCerts to the absolute path of a PEM file with the extra certificates.
• Keep http.proxyStrictSSL on. Turn it off only briefly while troubleshooting, or when your administrator requires it, because it disables certificate checks.

{
  "http.proxy": "http://proxy.example.com:8080",
  "http.noProxy": ["localhost", "127.0.0.1", ".example.internal"],
  "hull-code.new.extraCaCerts": "/absolute/path/to/corporate-ca.pem"
}

Move from an older versionCopy Anchor Link

If you used an earlier version of the extension, run Hull Code: Migrate Settings from Legacy Version to bring across your providers, MCP servers, custom modes, default model, settings and sessions. See Custom agents for how old modes map to agents.

TroubleshootingCopy Anchor Link

See Troubleshooting to collect logs and fix common problems.