# Cactus: AI help center and support agent from your code

Cactus learns a product from its codebase, answers its customers live, and keeps its help site and changelog current with every release.

## Built for teams that ship faster than they can document.

Cactus learns your product from the code and explains it to anyone who asks.

## Every release makes yesterday's answers a little more wrong. Cactus rewrites them while you build.

Under the line, the help page "Signing in" on Pied Piper Docs, with 3 releases landing beside it that each make one of its facts wrong, then Cactus rewriting each one in place.

## Docs that keep up with your code.

Cactus writes your help site from your code. When you ship, it rewrites the pages your change touched, the same day.

Anything you write yourself, Cactus leaves alone.

Beside it, the app with the help page "Resetting your password" open, written from Pied Piper's code.

## Live support that knows your product.

Customers ask in your product or on your help site. Cactus answers right away and shows the page it used.

If they'd rather talk to a person, your team takes over with the whole conversation.

Beside it, the Inbox open on Maya Osei's conversation as Cactus answers it: her question "If we compress our video library, can we still get the exact original files back?", and Cactus' answer "Getting your original files back" from the help page "Restoring original files".

## And your docs are agent ready.

Customers ask Claude, ChatGPT and Cursor about your product too. They read your help site and give the same answer Cactus would.

There's nothing to set up.

Beside it, a customer asks Claude, ChatGPT, Cursor, Claude Code, WebMCP or any other client "How long does a password reset link last in Pied Piper, and how do I get a new one?" and gets the same answer, from the help page "Resetting your password" on docs.piedpiper.com.

[How an AI client reads your help site](/mcp)

## Ask Cactus about Cactus.

### What do I have to write?

Nothing. Cactus writes the help site from the code. Anything you'd rather say yourself, edit, and it stays.

### How long does it take to set up?

About five minutes. Connect your code, and Cactus reads it and writes your whole help site while you wait. From then on, ship a change and the pages it touched are rewritten the same day, with a Changelog entry to match.

### Can customers trust the answers?

Each answer comes from what the code actually does and names the help page behind it, so a customer can read on. Each page cites the commits it was written from.

### Where can customers ask?

In your product, on your help site, or from Claude, ChatGPT or Cursor. The answer is the same everywhere, with the help page behind it.

## Keep shipping. We'll handle the explaining.

Invites go out in order. We'll write when yours is ready.

[Join the waitlist](https://heycactus.ai/#waitlist)