Product setup finishes after pages publish New
Aug 28–30, 2026 · Teamspace and product setup
Product setup takes you from a named product through published help pages, so you can start managing it with a clear next step.
Cactus reads your teamspace's company domain for branding and keeps the accent color you choose. The completion card waits until help pages publish, and connecting GitHub takes you back to the product you left.
A teamspace for your work email
With a work email, Cactus creates a teamspace named after you or offers a one-click join when your email domain already has one. Naming it for you keeps the teamspace distinct from your product's brand.
Connect GitHub without account linking
When you connect GitHub, Cactus verifies installations you control through GitHub's authorization return, without asking you to link your GitHub identity to your Cactus account. If you haven't installed the GitHub App, the flow takes you to its install page.
Improvements
- Help pages suggestions use Product Map questions, and findings without a page can get one
- Product knowledge investigations cover repository history and product context, read the full README, and save findings as evidence
- Help pages page rewrites start cleanly, use product terms, and share an editorial plan
- Answers the answer bubble shows real reasoning, and live turns keep learned context
- Release updates changelog entries use commit dates and group by month or quarter
- Product pages product pages use product-specific URLs, with article pages in the path
- Help Center in-app docs add breadcrumbs, audience toggles, changelog pages, and concept hover cards
- Navigation the app has a top navigation bar
Fixes
- Builds builds finish without getting stuck on long-running model or sandbox calls
- Inbox conversation anchors leave space for the byline
- Release updates the changelog update survives a missing source checkout
- Navigation app navigation remains visible outside a product
- Product knowledge findings update the right page, dead links stay gone, and indexing failures don't stall the Product Map
- Appearance picker transitions work again, and brand fills keep their text readable
- Products invalid product links no longer cause an error page
- Help pages failed pages can be retried, dead markers stay hidden, and docs questions save in the catalog
- Product sources blocked source pages can still load through another fetch route
- Answers a new question starts with a clear reasoning bubble
85 commits