Veil v1.2.4

Veil Extension v1.2.4

Installation

1. Download veil-extension-1.2.4.zip below
2. Extract the zip file
3. Open Chrome -> -> Enable Developer mode
4. Click Load unpacked and select the extracted folder

Local Server Install / Update

Linux/macOS:

Windows:

Local Server Uninstall

Linux/macOS:
Veil local server is not installed at /home/runner/.local/share/veil.

Windows:

Chrome Web Store

Submit the zip to the Chrome Web Store Developer Console.

Changelog

[1.2.4] - 2026-04-02

Update UX and Backend Tracking

• Split extension and backend release state in the popup/settings UI so Veil can clearly show mixed states like “extension behind, backend already updated” instead of masking backend success behind one generic update warning.
• Refreshed release-state checks whenever the popup or settings view regains focus, reducing the need to close and reopen Veil after refreshing the local server bundle.
• Surfaced missing backend release metadata as a one-time refresh step instead of incorrectly implying that the installed backend is definitely outdated.
• Fixed Unix release metadata stamping so the stored backend html_url is extracted from the actual GitHub release payload instead of occasionally capturing an unrelated nested URL.
• Embedded canonical release metadata directly into the backend bundles so local installs can verify the installed server version even when api.github.com is temporarily rate-limited or unavailable.
• Updated the Unix and Windows installers to stamp .runtime/bundle_release.json from the bundled metadata and add installed_at locally instead of depending on a live GitHub API call during install.
• Changed the settings popup/update surface to treat GitHub latest-release lookups as best-effort only: Veil now shows a verified local bundle state when installed metadata is known, and falls back to “backend version unknown” when both GitHub and local metadata are unavailable.

Settings and Maintenance

• Fixed settings-page sidebar navigation so section headers land fully below the sticky control bar, improved bottom-of-page scroll-spy behavior, and made the About section reliably selectable.
• Moved local server uninstall into Diagnostics so setup, logs, runtime details, and repair actions live in one Local Server workflow.
• Polished the Local Server maintenance surface with clearer recovery copy and a more explicit uninstall command section for removing the native host, autostart entry, and installed backend bundle.

Regex Detection

• Unified Veil’s built-in sensitive-token patterns into one shared regex catalog used by the background runtime, popup/options editor, and content-side settings normalization, eliminating drift between UI and detection behavior.
• Updated the online regex toggle to govern all regex-based detectors while GLiNER is healthy, while keeping regex fallback automatic when the local server is offline.
• Switched new installs and unset profiles to default to AI + Regex so structured secrets are protected alongside GLiNER from the first run.
• Expanded the built-in regex catalog coverage for GitHub tokens, IPv6, PAN, Aadhaar, passport, IFSC, and Indian driver-license patterns, and ensured explicit regex replacements are respected even in anonymize mode for token-style detections.
• Added a dedicated built-in MAC-address detector so colon-delimited MAC values no longer get mislabeled as IPv6 placeholders during regex protection.
• Added a shared regex smoke corpus and hostile-editor E2E fixtures so built-in and custom regex detectors are verified in online, offline, and internal-scroll scenarios without depending on a live local server.

Overlay and Onboarding Polish

• Reworked hostile-editor overlay refresh so external highlight boxes are rebuilt from tracked state, clipped to the visible editor scroll bounds, and refreshed through one anchored UI scheduler instead of lingering as stray floating boxes during Gemini-style internal scrolling.
• Stabilized hostile-editor overlay highlights by updating them in place instead of destroying and recreating them on every layout pass, reducing visible flicker in Gemini/Claude-style editors.
• Added a stable hover-intent reveal card for redacted hostile-editor overlays so original text stays readable while moving the pointer from the token to the reveal card.
• Added clearer live regex-runtime status notes to popup and settings so users can tell whether Veil is currently running in AI only, AI + Regex, or Regex fallback mode.
• Updated the setup flow styling to keep button text readable on hover and align the onboarding surface with Veil’s dashboard color language.

Privacy Hardening

• Removed inline response de-anonymization from provider-owned chat threads so Veil no longer writes original PII back into ChatGPT/Gemini/Claude-style message history.
• Tightened ChatGPT input monitoring so historical user turns are never mistaken for live composer surfaces.
• Standardized anonymize-mode fallback so supported entities fall back to safe masking instead of alias placeholders when Maya anonymization is unavailable.
• Restored original PII only in assistant responses on the user’s device while keeping user-thread prompts permanently protected in provider-owned history.
• Improved staged refinement so Maya-supported labels like emails inherit their anonymized replacements after the fast local regex pass instead of remaining stuck in temporary mask placeholders.
• Clarified popup/settings copy that Maya anonymization is the trusted remote path for supported labels, unsupported detections stay local, and Diagnostics are local-only troubleshooting data.

Performance and Composer Protection

• Added a staged long-paste protection flow that applies fast local regex/custom masking first, then refines the same canonical source text with GLiNER and Maya anonymization in the background.
• Tightened send guards so Veil blocks submission while protection is still pending, preventing large pasted prompts from slipping through before refinement completes.
• Switched popup protection counts to compute from the live redaction state so the UI reflects the actual number of protected items on the page during staged refinement.

Windows Installer

• Changed the Windows PowerShell installer to treat autostart registration as a warning when permissions block scheduled-task creation, allowing the core backend/native-host install to finish cleanly in non-admin sessions.
• Added a safe immediate-start step after install on Windows so Veil can start the local server for the current session when port 8765 is free, while still warning instead of failing if the server is already running or the port is occupied.
• Replaced the previous cmd.exe-only manual start guidance in the Windows autostart script with both Command Prompt and PowerShell-safe instructions.