New Sep 28 – Oct 4, 2026

Help Center and knowledge answer checks

Cactus checks Help Center and product-knowledge answers, then investigates the code when those sources fall short. Teams can translate conversations, add help-page diagrams, publish AI-agent guidance, follow clearer release updates, and read AI visibility reports more easily.

  • Two checks before a reply.

    Cactus checks answers from Help Center pages and product knowledge before writing.

    If neither source can answer, it investigates the code and writes that finding as the reply.

  • Clearer release headlines.

    Release titles name their headline change, summaries lead with what shipped, and each release carries the category of its lead chapter.

    Updates join the open day’s release as commits arrive.

  • Product diagrams in help pages.

    Help pages can include diagrams of product sets and screen controls, with legends for sets and lifecycle states.

    Captions describe what readers see, while citations keep the source references.

  • An Agents page for your Help Center.

    Publish an Agents page explaining how to connect an AI agent to your product, or turn it off in Appearance, Help site.

    Browser agents can inspect and run tools on Developers. AI agents can read Developers and Contact as Markdown. Help-page text keeps links and heading levels.

1 more change
  • Plain-language AI search rankings.

    Visibility explains rankings in plain language.

    A long Slack card can omit phrases without a watched competitor in the top 10, and reports how many and where. The Visibility site separates models, shows top three recommendations and why, and sets Cactus mentions apart. Slack lets you mark or dismiss to-dos.

Read the help page: Answer customer questions with Cactus

39 smaller changes

Improvements

  • Conversations You can share, rate, or hand off a verified conversation from another device
  • Messenger Changed Messenger launchers to match saved settings across themes, styles, and host pages
  • Handoffs Changed help-site and Messenger handoffs to appear in the Inbox with visitor context
  • Answers Changed answers to include fitting figures from cited product pages
  • Writing rules Changed writing rules to shape affected help pages and release chapters
  • Messenger Changed Messenger requests to omit unused visitor IDs and transcripts
  • Product knowledge Changed product maps to cite package files across monorepos
  • AI clients You can cancel an MCP ask without waiting for its response
  • Help Center Changed related-page lists to show up to four pages, ordered by product-map connections
  • AI clients Changed MCP and A2A asks to use the team owner’s tools when the owner asks
  • Product setup Changed product setup to use one team website and brand across products
  • Messenger Changed Messenger questions and retries to retain the help page the visitor was viewing
  • Discord Changed Discord investigations to post findings in the thread
  • Help pages Changed product-filled values on help pages to use readable labels instead of code placeholders
  • Help pages Changed state tables to live on their owning help page, with other pages linking there
  • Help pages Changed help-page organization to use short IDs and avoid proposing a page with a live page’s name
  • Product knowledge Changed first product maps to cover screens, connected services, settings, and public policies
  • Product knowledge Changed product docs to update while code indexing finishes
  • Images You can upload an image in app or Messenger chats, or attach one to a Rule
  • Featured pages You can feature up to eight help pages on the Help Center home
  • Help pages Changed chat messages so Cactus receives their attached pictures
  • What's New You can ask about shipped changes and read the answer in a What’s New page thread

Fixes

  • Teamspace Fixed invitation acceptance so teammates land in their teamspace
  • Slack Fixed previews for help-page links pasted into Slack
  • AI clients Fixed MCP database errors to show a plain sentence instead of SQL details
  • Inbox Fixed Inbox updates so each team sees only its own conversation turns
  • Repository sync Changed code indexing to read prepared files without following links outside the repository
  • Answers Fixed refused answers to use a plain fallback sentence, even when streamed
  • Products Fixed simultaneous setup so same-named products get separate addresses
  • App tray Fixed product renames to appear in the app tray immediately
  • Messenger Fixed Messenger answers for visitors identified by email alone
  • Builds Fixed cancelled builds so they stop instead of continuing as failed runs
  • Answers Fixed question retries to resend their original images
  • AI clients Fixed AI clients to sign in before fetching withheld pages
  • Page audiences Fixed page routing so pages for different audiences stay separate
  • Repository sync Fixed code changes to be included in product knowledge after each push
  • Help pages Fixed help-page generation so duplicate proposals share one page, live page names stay reserved, and retirements record their reasons
  • Help pages Fixed verification badges by removing them from help pages, answers, and Messenger’s Help Center view
  • Messenger Fixed Messenger threads on phones to stay within the page

269 commits