CactusSource names in product answers Improved
May 14–21, 2026 · Product knowledge
Cactus describes the sources behind its product knowledge in customer-facing language, so you can understand what an explanation draws on.
Product knowledge without internal labels
Generated explanations use customer-facing names for connected sources and leave internal source labels, repository-indexing terms, and drafting artifacts out.
Answers that reflect your audience
Answers describing your product draw on audience and customer-workflow facts, while leaving distribution and route details out.
Product updates in customer language
Timeline updates draw on refreshed product facts and use customer-facing language. They avoid unsupported timing and universal claims, and leave code-like evidence details out.
Improvements
- Repositories GitHub refreshes with operational-only changes are skipped
- Sign in web chat models load only when a portal route needs them
- Help pages help pages use clearer source descriptions and leave implementation labels out
- Product knowledge public-facing copy can include product-understanding details
188 commits