Feat/gateway security hardening - #77
Merged
Merged
Conversation
- Replace URL API tokens with short-lived, single-use bridge codes. - Revoke active sessions when the gateway stops, restarts, or reconnects. - Reset the watchdog only for authenticated gateway activity. - Add a configurable idle timeout while keeping the 30-minute default. - Require trusted browser events for approval modal actions.
- Install the bundled bridge under a stable app-data path with a fixed extension identity. - Stage and validate bridge builds while coordinating concurrent VS Code windows. - Restart only active isolated browser profiles before activating an updated bridge. - Negotiate bridge protocol versions and explain stale extension recovery.
- Preserve profile detection across POSIX paths and supported Chromium executables. - Detect every process using the shared bridge before activating a staged build. - Serialize activation and launch, and reclaim stale install locks atomically.
- Acquire install locks with exclusive directory creation on every platform. - Raise process-list buffering and cover output beyond the Node default.
- Model extension runtime messages as discriminated unions with scoped background dispatch. - Validate message payloads and reject unknown or malformed message shapes. - Add coverage for valid variants, invalid payloads, and background message routing.
- Prepare eval and QA browser extensions with the stable bundled extension identity. - Load the prepared bridge in deterministic, command-risk, and DeepSeek browser runs. - Reuse local VS Code for Extension Host tests while keeping CI downloads explicit.
- Use the Chrome Web Store public key for standalone ZIP and VSIX browser builds. - Restrict bridge redemption to the shared extension identity. - Reject prebuilt manifests with missing or mismatched identity keys before bundling.
- Validate lock directory snapshots and use stable identities during stale lock reclamation. - Keep QA, E2E, and DeepSeek browser extension installs inside each run directory. - Add regression coverage for overlapping reclaimers and inherited installation root overrides.
- Sort normalized relative paths consistently when packaging and validating bridge builds. - Store development and test host bridge installs separately from production installs. - Preserve explicit browser extension root overrides in every host mode.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.