ShadowGlass, find shadow AI in firewall logs on-device
ShadowGlass Your logs never leave your browser. ShadowGlass reads the log file you give it, does every bit of analysis locally in the Chrome side panel, and makes no network request at all. You can confirm this yourself by reading the manifest.
- ▪ShadowGlass Your logs never leave your browser.
- ▪ShadowGlass reads the log file you give it, does every bit of analysis locally in the Chrome side panel, and makes no network request at all.
- ▪You can confirm this yourself by reading the manifest.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,495 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/JustinNarracott/ShadowGlass |
| Publication time | Mon, 27 Jul 2026 19:27:26 +0000 |
| Retrieval time | 2026-07-27T19:53:58.939Z |
| Last seen | 2026-07-27T19:53:58.939Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | kFrFn5wPTmP4 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
ShadowGlass Your logs never leave your browser. ShadowGlass reads the log file you give it, does every bit of analysis locally in the Chrome side panel, and makes no network request at all. Not one. You can confirm this yourself by reading the manifest. Find the shadow AI in your firewall and proxy logs, entirely on your own machine, using the AI already built into Chrome. What it is ShadowGlass is a Chrome side-panel extension for security and IT teams who want to know which AI providers and models their organisation is actually calling, without uploading a single log line to anyone. You already have the evidence, in your firewall or proxy export. ShadowGlass turns it into an inventory.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.
Discussion
0 commentsMore from GitHub
