chore(main): release 2.38.1#813
Conversation
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
7933ee1 to
9ac03c6
Compare
|
/wizard-ci sample |
🧙 Wizard CI ResultsTrigger ID:
Configuration
|
|
/wizard-ci-snapshots next-js |
|
To test:
|
|
/wizard-ci-snapshots basic-integration/next-js |
🧙 Wizard CI ResultsTrigger ID:
Configuration
|
✅ Remark-to-prod verified on the RC (
|
| Axis | Value | Source |
|---|---|---|
| harness | pi |
[switchboard] decision … harness=pi (cli) |
| model | openai/gpt-5.4 |
model=openai/gpt-5.4 (cli) |
| effort | low |
capability default for gpt-5.4 (models.ts), no override passed |
| sequence | linear |
(pi-clamp) — pi has no runTask |
| gateway | gateway.us.posthog.com/wizard/v1 (openai-completions) |
run log |
| run | completed, posthog-js + posthog-node added, .env.local written |
result JSON |
#806 actually exercised
The model's output for the final turn contained both the instruction echo (Stop-hook feedback re-stating the ask) and a real remark — exactly the collision #806 fixes. remark() walked the matches, dropped the echo (REMARK_INSTRUCTION.includes(text)), and returned the real line:
[WIZARD-REMARK] It would have helped to state explicitly that this repo initially
contained only `package.json` and no app source files, clarify whether creating a full
starter Pages Router structure from scratch was expected, warn that `read` on nonexistent
target files will fail before first creation, and document an allowed verification command
for Next.js projects that lack `package.json` scripts.
That non-echo line is what analytics.capture('wizard remark', { remark }) sends. The client is the real one (ANALYTICS_HOST_URL = internal-j.posthog.com, flushAt: 1) — not muted in the e2e path — and the run flushed on completion.
Caveat: I verified the whole path up to the wire (remark extracted → capture() on a live, immediate-flush client). The final row in internal-j isn't readable with my us-cloud creds, so the instance-side confirmation is a team-side check — but nothing between the remark and the POST is stubbed.
Full snapshot journey — 33 frames captured (29 run-progression frames collapsed; distinct screens below)
01 · intro
PostHog Wizard v2.38.1 Feedback: wizard@posthog.com
███ PostHog Wizard 🦔
We'll use AI to analyze your project and complete work.
.env* file contents will not leave your machine.
Let's do two hours of work in eight minutes.
Directory ✔ /wizard-remark-1file-pi
Framework ✔ Next.js (detected)
▸ Continue
Change framework
More info
Cancel
02 · health-check
PostHog Wizard v2.38.1 Feedback: wizard@posthog.com
╭──────────────────────────────────────────────────────────────╮
│ Ongoing service disruptions │
│ ◼ Down ◼ Degraded ◼ No connection │
│ ◼ Anthropic │
│ The Wizard cannot start while these services are down. │
│ You can still download the PostHog integration skills and │
│ continue with another agent. │
│ Continue anyway? │
│ ▸ Continue [Enter] Download skills & Exit [Esc] │
╰──────────────────────────────────────────────────────────────╯
(Anthropic flagged degraded — irrelevant here, the run is on openai/gpt-5.4 via the gateway.)
03 · setup
PostHog Wizard v2.38.1 Feedback: wizard@posthog.com
Project Setup
Configuring Next.js integration
Which Next.js router are you using?
▸ App Router
Pages Router
29 · run (final frame — all tasks done, cleaning up)
PostHog Wizard v2.38.1 Feedback: wizard@posthog.com
Tips Tasks
◆ You can also track people and groups ◼ Analyze project
with PostHog ◼ Set env vars
◼ Install SDK
◆ Get way more detail using properties ◼ Initialize PostHog
◼ Instrument events
◆ Use PostHog in Slack ◼ Verify
◼ Create dashboard
◼ Write setup report
⠴ Cleaning up...
──────────────────────────────────────────────────────────────────────
┊ Finding and correcting import issues.
◆ Fixing project wiring and tightening analytics properties.
30 · outro
PostHog Wizard v2.38.1 Feedback: wizard@posthog.com
✔ Successfully installed PostHog!
Dashboard: https://us.posthog.com/project/228144/dashboard/1807672
Check ./posthog-setup-report.md for details
What the agent did:
• Analyzed your Next.js project structure
• Created and configured PostHog initializers
• Integrated PostHog into your application
• Added environment variables to .env file
Events added: login_submitted, login_succeeded, login_failed,
logout_clicked, burrito_considered, profile_error_test_triggered,
server_login_processed, server_login_validation_failed, hello_api_requested
31 · mcp
PostHog Wizard v2.38.1 Feedback: wizard@posthog.com
Install the MCP so you can chat to your data
Detected: Claude Code, Claude Desktop/Web, Cursor, Visual Studio Code, Zed
Install the PostHog MCP server and plugin?
▸ Install with all features (recommended)
Customize features
No thanks
32 · slack-connect
PostHog Wizard v2.38.1 Feedback: wizard@posthog.com
@PostHog in Slack
Ask about your product data, debug issues, and generate PRs.
▸ Open Slack setup
Skip / Continue
33 · keep-skills
PostHog Wizard v2.38.1 Feedback: wizard@posthog.com
Keep the skills?
.claude/skills/integration-nextjs-pages-router/
Source: https://github.com/PostHog/context-mill
▸ Keep [Enter] Remove [Esc]
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
2.38.1 (2026-07-06)
Bug Fixes
This PR was generated with Release Please. See documentation.