VS Code Extension
Hide API keys, tokens, and .env secrets before you share your editor
ContextBlur for VS Code is built for developers who stream, pair program, record tutorials, demo features, or code in public. Keep real code visible while sensitive values stay hidden.
Free to start · VS Code 1.75+ · macOS, Windows, Linux
ext install Smerda.contextblur
Best fit
Developers who share real code
Built for live demos, pair programming, onboarding, conference talks, and AI coding sessions where real secrets sit too close to the code you need to show.
Core risk
Secrets leak in normal workflows
The biggest risks are not dramatic breaches. They are .env tabs, terminal output, copied tokens, extension settings, and internal IDs that show up during ordinary coding.
Why it matters
Developer trust breaks fast
A visible key, repo name, or internal URL can derail a demo, create cleanup work, or force teams into fake environments that drift from reality.
Explorer
Editor values and risky filenames stay hidden before the share begins.
Feature Fit
Built for coding demos, not generic editor cosmetics
Each feature exists to reduce real secret exposure in tutorials, team calls, AI coding sessions, and public walkthroughs.
Auto-detect sensitive patterns
Blur API keys, tokens, .env values, connection strings, and other obvious secrets as soon as the file is visible.
Explorer-safe file names
Hide `.env`, `secrets.*`, `credentials.*`, and other risky filenames in the VS Code sidebar before you start sharing.
Presentation mode
Use one toggle before streams, walkthroughs, or pair sessions so the editor is ready before anyone sees your screen.
Custom regex patterns
Match internal IDs, proprietary tokens, customer-specific patterns, or whatever your stack exposes that generic scanners miss.
Team-shared configs
Keep the whole team aligned with version-controlled config patterns for repeated demos, onboarding, and recorded walkthroughs.
Live Share support
Keep sensitive values hidden during collaborative editor sessions instead of relying on everyone to remember what not to open.
Workflow
Use the right extension for the right surface
VS Code protects the editor. The browser extension protects the dashboards, cloud tools, and tabs you show alongside it.
| Scenario | Best tool | Why |
|---|---|---|
| Sharing `.env`, source files, terminals, and explorer panels in VS Code | VS Code extension | The risk lives inside the editor surface itself. |
| Showing Vercel, Supabase, Stripe, AWS, or admin dashboards during a coding demo | Browser extension | The risk is in browser UI, settings pages, and cloud dashboards. |
| Switching between code and browser during a tutorial or onboarding call | Both | Use VS Code for editor secrets and the browser extension for cloud and admin surfaces. |
Install Flow
Three steps before the next coding session
This is the path you want for onboarding videos, technical demos, pair sessions, and streaming.
Install the extension
Search "ContextBlur" in VS Code Extensions, run `ext install Smerda.contextblur`, or use the Marketplace button.
Open the real project
Use the project, `.env`, logs, or config files you actually demo from so protection matches the real workflow.
Enable before you share
Turn on presentation mode or secret detection before anyone can see the editor surface.
Pricing
Start free. Upgrade when coding demos become routine.
Free is for validating the workflow. Pro is for teams and developers who keep hitting the same secret-exposure patterns.
Free
- Auto-detect common secret patterns
- Blur risky filenames in the explorer
- Presentation mode for coding sessions
- Live Share-friendly setup
Best if you want proof of value before making the workflow part of your team's demo process.
Install FreePro
- Everything in Free
- Custom regex patterns for your stack
- Team-shared configs for repeatable demos
- Lower-prep setup for recurring sessions
Best when the extension becomes part of your regular demos, onboarding, livestreams, or team coding workflow.
Get ProDeveloper Guides
The exact guides that should feed the VS Code funnel
These pages capture the strongest developer-intent queries around API keys, GitHub, AI coding, and secure screen sharing.
FAQ
Common questions from developer teams
Use this to decide if the VS Code workflow should stay a solo tool or become part of your recurring team setup.
Who is ContextBlur for VS Code best for?
It is best for developers who regularly stream, record tutorials, pair program, onboard teammates, or run coding demos where real secrets and internal identifiers can appear on screen.
What does the VS Code extension protect?
It helps hide API keys, tokens, .env values, explorer file names, internal identifiers, and other sensitive strings that show up in editors, sidebars, and coding workflows.
When should I use the VS Code extension instead of the browser extension?
Use the VS Code extension when the risky surface is your editor itself. Use the browser extension when the sensitive data lives in dashboards, admin tools, cloud settings, or browser tabs you present alongside your code.
When does Pro make sense for VS Code?
Pro makes sense when your team shares code often enough to want custom regex rules, shared configs, and a repeatable setup across developers instead of one-off manual prep.
Install it on the editor you actually demo from
If you share real code, the fastest win is to protect the editor surface before you start speaking. Use the browser extension as the companion layer for dashboards, cloud tools, and tabs.
100% local processing. Your code does not leave your machine.