Docs
Context Buzz
Stars and issue counts do not tell you how people work with your product. Context Buzz reads GitHub activity tied to your listening terms and groups it by how the product is being used.
What it tracks
Every relevant GitHub mention is placed into a usage bucket so you can see the shape of adoption at a glance:
- Adopting. Someone is setting the product up for the first time.
- Integrating. Someone is wiring it into their own stack.
- Extending. Someone is building on top of it or around it.
- Operating. Someone is running it day to day.
- Migrating. Someone is moving to it or away from it.
- Exploring. Someone is kicking the tires.
Blockers are labeled separately: bug, missing feature, documentation gap, performance, developer experience, or none. Each entry links back to the real issue, discussion, or comment it came from.
Your customer's language
Context Buzz keeps code, error messages, package names, and URLs exactly as written, and can carry a translated summary when the original post is not in English. Your workspace reply-language preference controls the summary language.
Context Buzz is read only. It summarizes what developers already said in public and never posts or comments anywhere. Issues and pull requests live in other people's repositories, so EarShots does not draft replies for them either. Use what you learn there in your own product, docs, and roadmap.