Skip to main content
Vibrancy Continued provides three commands that you can access through the Command Palette to manage the extension’s behavior.

​
Accessing Commands

All commands can be accessed through the Command Palette:
1

Open Command Palette

Press F1 or Ctrl+Shift+P (Windows/Linux) / Cmd+Shift+P (macOS)
2

Search for Command

Type “Vibrancy” to see all available commands
3

Execute Command

Select the command you want to execute

​
Available Commands

​
Enable Vibrancy

​
extension.installVibrancy
command
Command ID: extension.installVibrancyDisplay Name: Enable VibrancyInstalls and enables the Vibrancy effect in VS Code. This command:
  • Modifies VS Code’s internal files to inject the vibrancy runtime
  • Applies the selected theme from your settings
  • Configures window transparency and blur effects
  • Prompts you to restart VS Code to apply changes
After running this command, you’ll see a message about VS Code being “corrupt.” This is expected behavior. Click the cogwheel icon and select Don’t Show Again to dismiss it permanently.
When to use:
  • First time setup after installing the extension
  • After VS Code updates (the extension will prompt you)
  • When re-enabling after disabling

​
Disable Vibrancy

​
extension.uninstallVibrancy
command
Command ID: extension.uninstallVibrancyDisplay Name: Disable VibrancyRemoves the Vibrancy effect and reverts VS Code to its default state. This command:
  • Removes all modifications from VS Code’s internal files
  • Restores original VS Code settings
  • Cleans up runtime files
  • Prompts you to restart VS Code
When to use:
  • When you want to temporarily disable the effect
  • Before uninstalling the extension
  • To troubleshoot issues with VS Code
  • When switching to a different transparency extension

​
Reload Vibrancy

​
extension.updateVibrancy
command
Command ID: extension.updateVibrancyDisplay Name: Reload VibrancyUpdates the Vibrancy installation with current settings. This command:
  • Uninstalls the current Vibrancy configuration
  • Reinstalls with your updated settings
  • Applies theme changes
  • Prompts you to restart VS Code
When to use:
  • After changing Vibrancy settings (theme, opacity, type, etc.)
  • After VS Code updates
  • When the effect stops working correctly
  • To refresh the extension after configuration changes
The extension will automatically prompt you to reload when you change settings, but you can also run this command manually.

​
Command Usage Examples

​
Initial Setup

# After installing the extension
1. Press F1
2. Type "Enable Vibrancy"
3. Press Enter
4. Click "Restart Visual Studio Code" when prompted

​
Changing Settings

// settings.json
{
  "vscode_vibrancy.theme": "Tokyo Night Storm",
  "vscode_vibrancy.opacity": 0.5
}
After changing settings: 
1. Press F1
2. Type "Reload Vibrancy"
3. Press Enter
4. Click "Restart Visual Studio Code" when prompted

​
Troubleshooting

If the effect isn’t working:
1

Disable Current Installation

Run Disable Vibrancy command
2

Restart VS Code

Close and reopen VS Code completely
3

Enable Again

Run Enable Vibrancy command
4

Restart Again

Restart VS Code one more time

​
Command Palette Shortcuts

You can create custom keybindings for these commands: 
// keybindings.json
[
  {
    "key": "ctrl+alt+v",
    "command": "extension.updateVibrancy"
  },
  {
    "key": "ctrl+alt+d",
    "command": "extension.uninstallVibrancy"
  }
]

​
Automatic Updates

The extension automatically detects when VS Code is updated and will prompt you to reload Vibrancy: 
// The extension checks version on activation
const currentVersion = context.extension.packageJSON.version;
let lastVersion = context.globalState.get('lastVersion');

if (checkRuntimeUpdate(currentVersion, lastVersion)) {
  vscode.window.showInformationMessage(
    localize(updateMsg), 
    { title: localize('messages.installIde') }
  ).then(async (msg) => {
    if (msg) {
      await Update();
    }
  });
}

​
Permission Requirements

On Windows, you may need to run VS Code as Administrator to execute these commands if you’re using the System Installer.On macOS, if you get permission errors, you may need to take ownership of the VS Code application files. See the Troubleshooting guide for details.
After running commands, you may want to adjust these settings:
  • vscode_vibrancy.theme - Select which theme to apply
  • vscode_vibrancy.opacity - Adjust transparency level
  • vscode_vibrancy.type - Choose blur effect type
  • vscode_vibrancy.imports - Load custom CSS/JS files
See the Configuration guide for complete settings documentation.

Build docs developers (and LLMs) love

Get started for freeTalk to us