Show HN: Chrome ext to let zot, your terminal coding agent, operate the browser
A new Chrome extension called zot-chrome-operator allows users to interact with their terminal coding agent, zot, directly from the browser. The extension enables zot to manage browser tabs and perform various actions through a side panel. Installation requires setting up a local bridge and configuring the environment to ensure proper functionality.
- ▪The zot-chrome-operator Chrome extension facilitates communication between the zot terminal agent and the Chrome browser.
- ▪Users must install the extension and set up a local bridge to enable browser actions.
- ▪The extension allows users to manage tabs, navigate pages, and interact with web content directly from zot.
2 outlets in our directory ran this story, first to last over 12 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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/patriceckhart/zot-chrome-operator |
| Publication time | Wed, 20 May 2026 06:48:00 +0000 |
| Retrieval time | 2026-05-20T07:05:00.570Z |
| Last seen | 2026-05-20T07:05:00.570Z |
| 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 | ONEr1CsVrw_W · 2 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
zot-chrome-operator Chrome extension + local bridge for chatting with zot from a Chrome side panel and letting zot operate browser tabs through a browser_action tool. Install Install directly as a zot extension, then install the zot-chrome command shim: zot ext install https://github.com/patriceckhart/zot-chrome-operator node "$HOME/Library/Application Support/zot/extensions/zot-chrome-operator/bin/install-cli.js" This does not require any changes to zot. The second command creates a global zot-chrome shim at: ~/.local/bin/zot-chrome Make sure ~/.local/bin is on your PATH. For example, add this to your shell profile if needed: export PATH="$HOME/.local/bin:$PATH" Why the second command? zot ext install only clones/copies extension files; it does not execute install hooks.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.