Skip to main content
The PromptGuard VS Code extension highlights unprotected LLM SDK calls in your code and provides quick fixes to add protection.

Installation

From VS Code Marketplace

  1. Open VS Code
  2. Go to Extensions (Cmd/Ctrl + Shift + X)
  3. Search for “PromptGuard”
  4. Click Install

From Command Line

From VSIX

Download from GitHub Releases:

Features

Inline Diagnostics

Unprotected LLM calls are highlighted with squiggly underlines:
  • Red (Error): Unprotected calls in production code
  • Yellow (Warning): Calls in potentially sensitive files
  • Blue (Info): Protected calls (informational)

Hover Information

Hover over a highlighted call to see:
  • Provider name (OpenAI, Anthropic, etc.)
  • Whether it’s protected
  • Link to fix or learn more

Quick Fixes

Click the lightbulb or press Cmd/Ctrl + . to see fixes:

Problems Panel

All findings appear in the Problems panel (Cmd/Ctrl + Shift + M):

Status Bar

The status bar shows protection status:
  • Protected — All LLM calls are secured
  • 3 unprotected — Click to see findings
  • Scanning… — Analysis in progress

Configuration

Settings

Open Settings (Cmd/Ctrl + ,) and search for “PromptGuard”:

settings.json

Workspace Settings

Create .vscode/settings.json in your project:

Commands

Access via Command Palette (Cmd/Ctrl + Shift + P):

Supported Languages

Supported Providers

The extension detects calls to:
  • OpenAI
  • Anthropic
  • Google AI (Gemini)
  • Cohere
  • AWS Bedrock
  • Azure OpenAI (detected via the OpenAI patterns — AzureOpenAI is a recognised class name)
The list comes from sdk-patterns.json, which the extension and the CLI both read. Mistral and Groq were previously listed but have never been in it, so the extension has never detected them.

Ignoring Findings

Inline Comment

File-level Ignore

Via Settings

Add to promptguard.exclude:

Integration with CLI

The extension uses the same detection engine as the CLI. If you have the CLI installed, the extension will use it for scanning:
Without the CLI, the extension uses a built-in scanner.

Troubleshooting

Check:
  • Is the file a supported language (.py, .ts, .js)?
  • Is promptguard.enable set to true?
Try:
  • Reload window: Cmd/Ctrl + Shift + P → “Reload Window”
  • Check Output panel for errors: View → Output → PromptGuard
Check:
  • Is the file excluded in settings?
  • Does the file have LLM SDK imports?
Try:
  • Run “PromptGuard: Scan Current File” manually
  • Check the Problems panel (Cmd/Ctrl + Shift + M)
Solutions:
  • Add test directories to promptguard.exclude
  • Use # promptguard-ignore comments
  • Lower severity to information
Solutions:
  • Disable scanOnSave for large projects
  • Add node_modules, .venv to exclude list
  • Install CLI for faster native scanning

Telemetry

The extension collects anonymous usage data to improve the product:
  • Extension activation events
  • Command usage counts
  • Error reports (no code content)
Disable in settings:
Or use VS Code’s global telemetry setting:

Changelog

v0.2.1 (February 2026)

  • Added AWS Bedrock provider detection
  • Improved TypeScript parsing
  • Fixed false positives in JSX

v0.2.0 (January 2026)

  • Quick fix actions
  • Status bar indicator
  • Workspace scanning

v0.1.0 (December 2025)

  • Initial release
  • Python and JavaScript support
  • Inline diagnostics

Contributing

The extension is open source:

Next Steps

CLI Tool

Scan from command line

GitHub Scanner

Scan repos on push and PR

Python SDK

Runtime protection

Node.js SDK

JavaScript protection