Context Buzz
Every repo, issue, and pull request that names your product.
Context Buzz reads public GitHub activity that references your product: repositories, issues, pull requests, and discussions. It shows what developers are building on top of you, which integrations they combine you with, and the errors and blockers that recur, for product and developer relations teams.
Usage themes
3 themes, 84 repositories
GitHub only, last 90 days
Token refresh in long-running jobs
38 repos
Blocked step: Exchanging a refresh token after the worker restarts
+2.4x since last month
Streaming responses with the Python SDK
27 repos
Blocked step: Reading partial chunks without buffering the whole reply
+0.8x since last month
Local eval harness setup
19 repos
Blocked step: Pinning model versions between runs
new this month
Reply drafting is turned off for repositories your workspace does not own. Context Buzz is for reading usage, not for contacting strangers.
What you see
Usage and blockers, side by side.
What they are doing
New repos, integrations, and projects built on top of your product, with a toggle to separate humans from agents.
What is blocking them
Grouped error strings, failing docs URLs, and open questions, each linked back to the source thread.
How it works
How activity becomes a pattern.
Each event is matched to your product by repo, package name, or docs URL. Errors are grouped by message, so ten people hitting the same wall show as one row with ten links. Agent-authored pull requests and issues are flagged, so you can separate human adoption from agent usage. Grouped friction feeds the Insights queue and the Stats rollup.
FAQ
Common questions
Does Context Buzz read private repos?
No. It reads public issues, discussions, and repository content only. Private repositories are never read.
How is a repo matched to my product?
By repository name, package name, or a reference to your docs URL. Each match is shown with the line that triggered it.
What is the agents toggle?
A filter that separates pull requests and issues written by coding agents from ones written by people, so you can read human adoption on its own.
Does it work for closed source products?
Yes, through references to your SDK, package name, or docs URLs in other people's public repositories.
Does EarShots reply inside these GitHub threads?
No draft is written for somebody else's repository.
Keep reading
See how developers use your product in code
Point EarShots at your product name and read what shows up on GitHub.