Theo Hide

Streamer-focused file protection for VS Code.

Prevents accidental leakage of sensitive files (like .env) during live streams or screen sharing. When a protected file is opened, Theo Hide intercepts the request and displays a safe "Restricted Access" screen instead of the file content.

Features

• Zero-Leak Guarantee: Uses the VS Code Custom Editor API to ensure file content is never rendered until explicitly confirmed.
• Native Confirmation: Immediately triggers a "Reveal?" Quick Pick prompt (Command Palette style) upon opening.
• Configurable: Easily add or remove protected file patterns via settings.
• Minimalist Design: Clean, theme-aware UI that blends perfectly with VS Code.

Installation

1. Install from Marketplace (Coming Soon) or manually via .vsix.

2. Build from Source:

   git clone <repository-url>
   cd theo-hide
   npm install
   npm run compile

Usage

Default Protection

By default, the following patterns are protected:

• **/.env
• **/.env.*

When you open a matching file:

1. The Leak Protection screen appears.
2. A prompt asks: "Reveal .env?"
   • YES: The file opens in the standard text editor.
   • NO: The file remains hidden.

Manual Unlock

If you dismissed the prompt, click the "Unlock File" button in the restricted view to trigger the confirmation again.

Configuration

Customizing Protected Files

You can add your own patterns (e.g., config.json, *.secret) in your VS Code settings (settings.json):

{
  "theo-hide.protectedFiles": [
    "**/.env",
    "**/.env.*",
    "**/config.json",
    "**/*.pem"
  ]
}

The extension automatically updates file associations when you save settings.

Restore Defaults

To reset the protected list to the original defaults:

1. Open Command Palette (Cmd+Shift+P / Ctrl+Shift+P).
2. Run: Theo Hide: Restore Default Protected Files.

Development

• Run: Press F5 in VS Code to launch the Extension Development Host.
• Package: vsce package to generate a .vsix installer.