The VS Code extension for Verboo Code does not live on the Marketplace yet: to install it, you package the source code and install the generated file straight from the editor. It takes under two minutes, and after that you get a Control Center, a chat shortcut, and terminal launches that always land in the right folder.
How do you install the Verboo Code extension in VS Code?
By packaging the source with vsce and installing the resulting .vsix from the Extensions panel. There is no official Marketplace listing, so searching "Verboo" and clicking install will not work.
git clone https://github.com/verbeux-ai/code.git
cd code/vscode-extension/verboo-vscode
npx @vscode/vsce package --no-dependenciesThe command produces a verboo-vscode-0.2.0.vsix file in the current folder. In VS Code, open the Extensions panel, click the ... menu at the top, choose Install from VSIX..., then select the file.
Just want to try it before installing for good? Open the vscode-extension/verboo-vscode folder in VS Code and press F5. That launches an Extension Development Host window with the extension already loaded, without packaging or installing anything.
Which commands does the extension add to VS Code?
Ten commands in the command palette, all prefixed with Verboo, plus one keyboard shortcut for chat.
| command | what it does |
|---|---|
Verboo: Open Control Center | opens the status panel in the Activity Bar |
Verboo: Launch in Terminal | opens a terminal and runs Verboo Code in the detected folder |
Verboo: Launch in Workspace Root | same, but forces the workspace root as the directory |
Verboo: New Chat | starts a new chat session in the side panel |
Verboo: Open Chat Panel | opens the chat panel (shortcut Ctrl+Shift+L, Cmd+Shift+L on Mac) |
Verboo: Resume Session | resumes the last chat session |
Verboo: Abort Generation | stops the generation in progress |
Verboo: Open Repository | opens the verbeux-ai/code repository in the browser |
Verboo: Open Setup Guide | opens the README's quick start |
Verboo: Open Workspace Profile | opens the project's .verboo-profile.json, if one exists |
What does the Control Center show?
Real status, not a guess. The panel reads the environment and shows:
- whether the command configured in
verboo.launchCommandis installed and available on PATH - the exact command that will be used to launch
- whether the
CLAUDE_CODE_USE_OPENAI=1shim will be injected into the terminal - which workspace folder is active
- what working directory (cwd) the launched terminal will use
- whether a
.verboo-profile.jsonexists at the project root - a provider summary, read from the saved profile or from known environment flags
When the extension is not sure where a piece of data comes from, it shows unknown instead of guessing. That is documented in the code itself, not implicit behavior.
Which folder does the extension launch Verboo Code from?
By priority: first the directory of the file open in the active editor, if it sits inside the workspace. With no active file, it falls back to the workspace root. With no workspace open at all, it uses VS Code's default terminal cwd.
There is one exception: if verboo.launchCommand points to a relative path instead of the global default verboo, the extension forces the workspace root, because a relative path only resolves correctly from there.
Which settings can you configure?
| setting | default | what it controls |
|---|---|---|
verboo.launchCommand | verboo | the command run in the integrated terminal |
verboo.terminalName | Verboo | the terminal tab's name |
verboo.useOpenAIShim | false | injects CLAUDE_CODE_USE_OPENAI=1 only into terminals the extension opens |
verboo.permissionMode | acceptEdits | controls which tool operations get auto-approved: default asks on every use, acceptEdits auto-approves file edits, bypassPermissions approves everything, plan is read-only |
Gotcha: verboo.useOpenAIShim only injects the environment variable into the terminal the extension opens. It does not pick or configure a provider on its own: if the workspace profile already sets a different provider, the extension will not silently override it.
The extension takes care of opening the right terminal in the right folder without manual work. What keeps the session going after that, without cutting context in half, is the engine behind it: on Verboo Code every session runs with unlimited tokens, so switching folders or resuming a session never costs starting the bill over.
