CactusCactus checks code when facts fall short Improved
Jun 28–30, 2026 · Answer customer questions
Cactus answers customer questions from your product knowledge, checking code when needed and following your team's guidance.
Cactus checks whether its evidence directly answers the question, then searches relevant code when facts are thin or only adjacent. Your product map, Rules, and lessons shape replies, which stream in chat with inline citations.
Customer answers leave code internals out
Customer-facing answers translate code-derived behavior into plain language and keep source paths, internal routes, architecture terms, and private names out of the prose. When code shows how a feature works, Cactus can still explain that behavior without exposing implementation details.
Follow investigations in chat
When Cactus starts a deeper investigation in chat, you can follow its current step and see the result when it finishes. The investigation's answer appears in the conversation instead of stopping at an in-progress status.
Customize Messenger's look and sound
In Connect, choose a Messenger launcher face and sound pack, then preview them alongside the conversation. Messenger loads your saved sound pack when it starts.
Improvements
- What's New browse release changes by quarter, month, or week, with summaries grouped into semantic chapters
- Product knowledge teach Cactus from gaps and conflicts, with frontend and backend behavior conflicts prioritized
- Product knowledge get product knowledge and generated answers sooner during indexing and refreshes
- Answers open cited sources from inline citations and per-source chips
- Answers follow streamed answers without the cursor jumping or getting in your way
- Getting started set up a product through a redesigned onboarding chat and selectable role list
- AI clients MCP clients start with the nontechnical internal view of answers
Fixes
- What's New release entries show their written descriptions instead of pull-request metadata
- Product knowledge source indexing, refreshes, and publishing recover more reliably from errors
- Answers open cited files in monorepos without broken GitHub links
- Answers see one consistent answer card across the catalog and chat, without duplicate entries
- Messenger read conversation history clearly in light mode
- Getting started onboarding continues into a product refresh without a frozen pipeline or stalled chat
- Product sources connect GitHub during product-source onboarding
- Cactus app the app can load product data through a fallback if its primary data client is absent
111 commits