Website request - "Install with AI" CTA on the context warehouse page
@ianmatson is already working on this.
Since Aug 24, 2026.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 907
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 430
Description
What do you need?
An "Install with AI" option next to "Get started" on /context-warehouse, so visitors can set up warehouse sources from the terminal instead of the browser.
The wizard has a warehouse subcommand that scans a codebase for databases and APIs and connects every source it finds, but the page does not mention it. Both CTAs on the page (mid-page and the one near the bottom) currently send everyone to in-app source setup.
Draft content
No Google Doc — this is a UI change, not new copy. The only new text is the button label "Install with AI" and the command it reveals:
- Shown:
npx @posthog/wizard warehouse - Copied:
npx -y @posthog/wizard@latest warehouse
Adding the option, not replacing "Get started". People who want the browser flow keep it.
References & examples
- #19453 — an agent-written PR that does this. Closed in favour of this issue. Treat it as a reference only, not a design: it adds a
ContextWarehouseCTAcomponent that renders both CTA slots on the page, with the command in a reveal panel below the buttons. - The homepage already pairs a primary CTA with a wizard command, and
WizardCommandhandles the show-clean/copy-pinned split. - Worth tracking clicks on each route so the split between browser and terminal setup stays visible. The homepage
homepagecta-*events are the naming pattern.
We looked at A/B testing CTA variants here first. The page does not get enough traffic to power it — detecting even a large relative lift in sources connected would take about eleven weeks — so a single additive change is the better call.
Deadline
None. This came up while writing a social thread about the context warehouse, where the question was where to point the CTA.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.