Setting up your first product
Setting up a product means creating it and then answering Cactus's setup conversation: the repositories it reads, your brand, any help pages you already have, where escalations go, and Linear. Once you save the repositories, Cactus starts the first build, and each verified owner is emailed once the first pages are live.
On this page
Create your product
Only a teamspace owner can create a product. A member sees "Only a teamspace owner can create a product." in place of the form, and is told to ask an owner.
Open New product. Its heading reads "Your first product" until the team has a product.
On your first product only, enter your company's name under Company. It is saved as your team's name, up to 60 characters.
Enter the product's name under Name, or under Product on a later product. It is up to 80 characters.
Select Create product. Cactus opens Home with the new product selected.
Start the setup conversation
On Home, a product still in setup shows one suggestion, "Set up" followed by the product's name. Picking it, or typing a question, starts the setup conversation.
Until every step is answered, the chat leads with Cactus's cards, and you reply to them.
Cactus asks the cards one at a time, in the order of the table below, and skips any step already answered.
If you leave before every step is answered, setup stays open, and the suggestion brings the conversation back where you left it.
Answer the five steps
Step | What Cactus asks | What happens to your answer |
|---|---|---|
Your code | What Cactus asks Which repositories the product is built from. | What happens to your answer Cactus reads these repositories to learn how the product works. |
Your brand | What Cactus asks Whether to use a colour read off your site. | What happens to your answer A picked colour becomes the colour your help site and Messenger wear. With no colour picked, the product uses Cactus' own theme. |
Help you already have | What Cactus asks Whether you have help pages somewhere already that Cactus can bring in. | What happens to your answer The step is marked answered, so it is not asked again. |
Escalations to your team | What Cactus asks Where a question that needs a person should go. | What happens to your answer The step is marked answered, so it is not asked again. |
Requests to Linear | What Cactus asks Whether bugs and requests people mention should be filed in your Linear. | What happens to your answer Connecting to Linear needs a workspace admin to pass Linear's consent screen. Skipping costs nothing, and the Linear connection stays as it was. |
Connect GitHub and choose repositories
Under Your code, the picker lists the repositories GitHub has given Cactus access to. If GitHub is not connected yet, the picker asks you to connect it first.
Connecting opens GitHub in a separate window, and the picker updates when you come back.
Select one or more repositories. Continue stays off until one is picked.
Select Continue to save the set.
If the set changed, Cactus starts the product's first build.
After the last step
Once every step is answered, Cactus says it is reading your code and writing your pages, which takes a few minutes.
The last card follows the build. Its one press closes setup and takes you into the app, and it counts the pages once they are live.
If the first build fails, the card says so, and your answers are kept. The Builds page shows why.
Once the first build has made pages live, each verified owner of the product gets one email. It says whether anyone can read the help site or only your team can.
Set up through an AI client
A person's AI client can take the same steps through the MCP server: get_setup first, then create_product, connect_source, choose and get_build.
The client needs the setup permission. Without it, get_setup says so and sets nothing up.
A client can connect sources the conversation does not ask about, such as help pages, Slack, Discord, PostHog, Intercom and LaunchDarkly.
Choosing GitHub repositories through choose starts the build when the set changed, and AI clients covers how a client is added.
If setup stops
What you see | What it means | What to do |
|---|---|---|
"No repositories yet" | What it means GitHub has not given Cactus access to any repository. | What to do Pick the repositories on GitHub, then come back to this step. |
"A GitHub admin still has to approve this install. You’ll get access once they do." | What it means The GitHub install is waiting on a GitHub admin. | What to do Ask a GitHub admin to approve it. |
"Couldn’t reach GitHub" | What it means GitHub did not answer the picker's request. | What to do Select Retry. |
"Pick at least one repository." | What it means Continue was pressed with nothing picked. | What to do Pick at least one repository, then select Continue. |
"Cactus couldn’t confirm the build started. Press again: it won’t start a second one." | What it means The save may or may not have started the build. | What to do Select Continue again. The same press is sent again, so only one build starts. |
"Cactus couldn't start reading these repositories. Try again." | What it means Cactus refused the build's start, and the previous set of repositories is put back. | What to do Select Continue again. |
"Couldn’t create this product. Try again." | What it means Creating the product failed. | What to do Select Create product again. |
If your plan has stopped Cactus, setup waits on an owner, who is sent to the plan page to choose a plan or fix a failed payment. Plans are set out on Plans and billing.
If you are not on a team yet, Cactus takes you to the welcome page first, and Joining a team covers that.