Wizard overview
Contents
Developers love the wizard. It started as the fastest way to get a deep, correct PostHog integration, without the hallucinations that come from naive agent-based attempts. It's growing into something more like a forward deployed agent.
Why a CLI
Users run the wizard with one npx command. This is a big reason it's so portable. Running a command feels better than copying and pasting a prompt into an agent, which is annoying. It works in any terminal, in any project, with no setup.
Because we own the harness, a run is unlikely to be affected by the user's local setup, their model preferences, or whatever else is polluting their agent's context. We can also track the success rate of real runs on the wizard dashboard, and use it to improve the docs.
What it does today
- Integrates PostHog. It installs the SDK and adds events across many frameworks. See the public docs.
- Sets up more products, like error tracking, revenue analytics, LLM analytics, and data warehouse sources.
- Audits an existing PostHog integration.
- Migrates a codebase from another analytics tool.
- Adds the PostHog MCP server to the user's editor.
Roadmap
Things we'd like to work on, in no particular order. For what we're doing this quarter, see the team's objectives.
- Iterative instrumentation. Start small and prove value, then give users more when they want it. Useful on day 1, day 10, and day 100.
- Better handoff to the user's agent. An opinionated first draft, with enough context for the user's agent to make it theirs.
- Better handoff to the PostHog app. Data already flowing when you open PostHog, plus suggested next steps: instrument more, improve data, build dashboards.
- Tracking new features. Instrument a newly shipped feature properly.
- Act as a forward deployed agent. Help audit, debug, and migrate a customer's setup.
- Performance. Every run gets faster and cheaper.
Who owns what
The wizard has a shared ownership model. The Wizard & Docs Team
Wizard & Docs Team owns the wizard as a harness, and makes it better for everyone. Product teams own the programs for their part of the product.
Blue is the Wizard & Docs Team
Wizard & Docs Team, green is another team, and dashed is coming soon. Surfaces run programs, and programs run on the platform.
New top-level command names need sign-off from the Wizard & Docs Team
Wizard & Docs Team, because a public command is hard to remove.
Programs live in src/programs/. CODEOWNERS requests reviews from the owner. For who owns each skill, see the context mill.
Ask questions in #team-wizard-and-docs.











