WeSearch

Microsoft – Agent Host Protocol for Running Agents in VS Code

·1 min read · 0 reactions · 0 comments · 28 views

Documentation for the Agent Host Protocol — a synchronized, multi-client state protocol for AI agent sessions

About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 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://microsoft.github.io/agent-host-protocol/
Publication timeTue, 26 May 2026 17:25:45 +0000
Retrieval time2026-05-26T17:37:50.291Z
Last seen2026-05-26T17:37:50.291Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryNone yet
Summary source textcontentText
Citation coverageNo WeSearch summary has been generated for this story yet.
ClusterrxgWfy1wyknr
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

📡Channels All the Way DownEvery push-style interaction lives on a URI-identified channel — root, sessions, terminals, changesets, and more. Every command and notification carries a top-level channel URI, so any message can be routed by inspecting (method, channel).

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