WeSearch
Show HN: Watch all the AI agents on your machine

Show HN: Watch all the AI agents on your machine

·9 min read · 0 reactions · 0 comments · 0 views
More from GitHub ai Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

all-your-agents Watch every coding agent on this machine, and inspect the sessions they leave behind. Compatibility Subagents covers start, end, background and nested. claude -p writes no live index entry, so a print-mode run appears in history only. Grok's tool_started carries no call id, so the current tool is identified by name.

Key facts
How this story was covered

2 outlets in our directory ran this story, first to last over 17 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 5,950 of its stories.

Original article
GitHub
Read full at GitHub →

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 publisherGitHub
Canonical URLhttps://github.com/markwylde/all-your-agents
Publication timeTue, 22 Sep 2026 10:57:49 +0000
Retrieval time2026-09-22T11:08:51.486Z
Last seen2026-09-22T11:08:51.486Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster1J2cTnTYYKkP · 2 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

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

all-your-agents Watch every coding agent on this machine, and inspect the sessions they leave behind. Compatibility Subagents covers start, end, background and nested. claude -p writes no live index entry, so a print-mode run appears in history only. Grok's tool_started carries no call id, so the current tool is identified by name. Two tools with the same name running at once show as one. A failed turn is reported as failed, but Grok records no error message for it, so activity.error is usually empty. grok -p registers as live only when GROK_TRACK_HEADLESS is set. Otherwise it appears in history only. Codex does not persist approval requests, so a session blocked on an approval reads as running. A launched Codex with no prompt yet has no rollout.

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub