Code citations in customer answers New
Sep 4–7, 2026 · Answer customer questions
Cactus investigates your product code when published help can't answer a question, then uses the findings to ground its reply.
Cactus investigates your product code
Questions the Help Center can't answer can trigger a code investigation. The answer lists the files it drew on for your team, while visitors get a single customer-safe source line.
Cactus answers in Slack threads
Cactus answers for the product linked to the channel, with the complete answer and links to cited Help Center pages. Follow-up mentions in the thread continue the same conversation.
Add a web page as a source
Attach a web page as a product source, and Cactus can use it alongside code when answering questions. It checks the page when it answers from it, and marks related help sections for refresh when the page's text changes.
Live answer progress
Messenger shows the steps in a reply as Cactus works, then streams the answer in readable text. If the turn fails, customers see the failure and can retry; when it finishes, the answer appears with its source cards.
Improvements
- Answer questions capped lists show how many items they leave out
- Help pages page progress shows each page's state and what each build step is doing
- Messenger citations open the Help Center they came from, and feedback stays with the answer you rated
- What's New each release has one date, and the live timeline fills in as releases are written
- Navigation the product picker, user menu, and page title move between views faster
- Cursor you can drag the cursor from its attachments, press its dot again after a pause, and it avoids menus
Fixes
- Help pages stale pages regenerate when opened, removed code marks affected pages, unanswered questions stay open, and page addresses persist
- Inbox the Setup filter is removed, and old links open the default Inbox view
77 commits