Add "Install with AI" alongside "Get started" on the context warehouse page

[ivanagas]

Changes

Adds an "Install with AI" button next to "Get started" on /context-warehouse, revealing npx @posthog/wizard warehouse (copying the pinned npx -y @posthog/wizard@latest warehouse). Both CTAs on the page render through a new ContextWarehouseCTA component, so a visitor gets one consistent path from top to bottom.

Additive rather than a replacement: "Get started" keeps its place and the terminal route is offered beside it, matching the pattern used elsewhere on the site.

Clicks are tracked as contextwarehousecta-getstarted-clicked / -installwithai-clicked / -copy-clicked, mirroring the homepage homepagecta-* naming. There's no experiment behind this — the events are there so the split between the two routes stays visible.

Why

The page was an outlier for offering no AI-install option at all, even though the wizard has a warehouse subcommand that scans a codebase and connects every source it finds rather than making you configure them one at a time.

This started out as an A/B test of three CTA variants, but the page doesn't get enough traffic to power it — detecting even a large relative lift in warehouse sources connected would have taken about eleven weeks, and anything subtler was out of reach. So the additive variant ships for everyone instead of waiting on a result we couldn't get. Earlier commits on this branch have the experiment scaffolding if it's ever worth revisiting at higher traffic.

Checklist

• I've read the docs and/or content style guides.
• Words are spelled using American English
• Use relative URLs for internal links
• I've checked the pages added or changed in the Vercel preview build
• If I moved a page, I added a redirect in `vercel.json` (n/a — no pages moved)

---

Created with PostHog from a Slack thread

[github-actions]

Deploy preview

Status	Details	Updated (UTC)
🟢 Ready	View preview	Aug 13, 2026 11:04AM

[github-actions]

Vale prose linter → found 1 errors, 0 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

src/components/ContextWarehouseCTA/README.md — 1 errors, 0 warnings, 0 suggestions

Line	Severity	Message	Rule
6:21	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash

[github-actions]

Bundle report

Total JS (gzip)

7.52 MiB (+0.4 KiB / +0.0%)

Eager graph (modules shipped in each entrypoint's initial chunks)

Entrypoint	Eager size	Budget	Modules
✅ app	16.86 MiB (no change)	report-only	2018

Largest modules in the app closure

Module	Size
./src/data/mcp-tools.json	989.7 KiB
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css	745.9 KiB
./src/components/Stickers/Stickers.tsx	696.4 KiB
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js	481.4 KiB
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules	395.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.cjs.js	364.8 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js	354.8 KiB
./src/hooks/useCustomers.tsx + 54 modules	354.5 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules	351.4 KiB
./src/components/ProductComparisonTable/index.tsx + 126 modules	296.6 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js	281.9 KiB
./src/components/SearchUI/index.tsx + 87 modules	273.0 KiB
./node_modules/.pnpm/@posthog+brand@0.8.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/magnifying-glass.mjs	254.7 KiB
./node_modules/.pnpm/framer-motion@10.18.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/framer-motion/dist/es/render/dom/motion.mjs + 109 modules	253.9 KiB
./node_modules/.pnpm/d3@7.9.0/node_modules/d3/src/index.js + 208 modules	247.4 KiB

---

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).

[ivanagas]

Closing this in favour of an issue, per Should I open an issue or a PR? — this changes how the page behaves, so the website team should own the implementation. The idea now lives in #19675, which links back here as a reference.