StackJack 0.1.0.12930+31bc2f9
StackJack 0.1.0.12930+31bc2f9
This release adds the AI Governance browser extension for Chrome, Edge and Firefox, which lets you control and record how staff use AI websites. It also adds a PII filter for connector results and fixes CompassOne tools that failed because CompassOne now requires a tenant ID.
New features
- AI Governance browser extension (Chrome, Edge and Firefox). A managed browser extension that applies an organization's AI policy to AI websites:
- Block or warn on unapproved AI sites, on personal (non-work) accounts and on file uploads.
- Check prompts, pastes and file uploads against your data-loss rules before they are sent. Depending on the rule, the send is allowed, masked or blocked. If the check cannot finish in time, the send goes through unchanged.
- Record activity at the capture level you choose: facts only, masked text or full text. With a text capture level, AI answers that follow the person's own send can also be recorded.
- Add tenant restrictions for approved vendors (Anthropic and OpenAI), so staff can sign in only to your approved vendor tenants.
- Keep enforcing the last policy the device received while it is offline. An optional Block when unreachable setting blocks named sites once that policy has expired.
- Update open tabs when the policy changes, without a page reload.
- Advanced policy options (site and account modes, upload mode and content inspection) require Pro or above. The lane itself can be turned on at any governed tier in regions where the extension is offered.
- Block page and requests. When a site is blocked, the person sees the reason in plain words and can submit a tool request from the block page. On a warning, they can choose to continue for the rest of the browser session. Data-loss rules still apply after they continue.
- First-run page. On first run, the extension shows a page where the person can have their own AI policy link emailed to them.
- Browser extension page in AI Governance. A new page under the Sources tab where you can:
- Turn the browser lane on and set the policy.
- Manage browser tokens. Rotate and revoke require a typed confirmation.
- See coverage by browser and version.
- Follow setup steps, including store listing status for each browser.
- Force-install through endpoint bundles. Endpoint bundles now include browser policy for each selected browser: a Windows registry file, macOS configuration profiles and a Linux policy file. Edge installs the extension from the Chrome Web Store listing. Intune macOS delivery sends the browser profiles alongside the existing Claude Code and Codex profiles.
- AI web apps in the inventory. AI web apps that staff visit in a managed browser now appear in the AI inventory as discovered items and raise the shadow-AI alert. Visiting a denied app raises the existing unapproved-tool alert.
- New browser alerts. You are alerted when the extension's support for a known AI site may be out of date, and when a browser token is refused.
- PII filter for connector results. A new per-organization switch on the AI Governance privacy page. When it is on, results from read-only connector tools that contain personal data are blanked before they reach the AI agent. An override is recorded as a single finding with a matching audit entry.
Improvements
- Windows and Linux installers now add the extension to the browser policy already on the machine instead of replacing it. Your existing force-install entries and Firefox extension settings are kept.
- The endpoint page explains why a selected browser was left out of a bundle. It also has notes on how Edge, Windows, macOS and Linux handle browser policy.
- Bundles are rebuilt automatically when a missing prerequisite for a browser becomes available, such as the lane being turned on or a token being created. They are also rebuilt when a browser token is rotated or revoked.
- Importing the Firefox registry file by hand no longer replaces your existing Firefox extension policy. A hand import does not force-install the extension on Firefox; use the installer script or Intune for that. The download notes and help pages now say this.
- Reviewers can now open the browser extension page and see browser tokens read-only. All changes on the page remain limited to administrators.
- The extension keeps working with policy settings added in newer StackJack versions. An unrecognized setting is treated as its least restrictive default instead of causing the whole policy to be rejected.
Bug fixes
- CompassOne:
- 31 scan, scan schedule, exposure and vulnerability update tools now accept an optional tenant ID. CompassOne now requires a tenant ID on these calls, so they previously failed with no way to supply one.
- When CompassOne refuses a call because the tenant ID is missing, the error now says to pass the tenant ID and is reported as a bad request, not as an API token problem or a retryable error.
- This error no longer counts against the connector's credentials.
UI & UX changes
- The rules page shows the "Browser extension" column, and includes the extension in the lane summary, only in regions where the extension is offered.
- The PII filter switch now explains that the filter takes effect only while data-loss scanning is active.
- The endpoint page has clearer messages for installer failures:
- The installer script needs to be imported again.
- A registry value could not be read or written.
- An existing browser policy could not be merged.
Breaking changes
- Endpoint bundles that deliver browser policy on Windows, or Firefox policy on Linux, need the updated installer script. An older script stops with an error asking you to update. Download the script again from the endpoint page and import it once. Bundles without browser policy are unchanged and keep working with the older script.
Known issues
- When answer capture is on, an answer recorded within ten minutes of a send may include content from a different conversation opened in the same tab.