Skip to content

feat(replay-vision): show deploy and replay checks in the outro - #1505

Open
ksvat wants to merge 1 commit into
mainfrom
posthog/replay-vision-outro-next-steps
Open

ksvat wants to merge 1 commit into
mainfrom
posthog/replay-vision-outro-next-steps

Conversation

@ksvat

@ksvat ksvat commented Oct 30, 2026

Copy link
Copy Markdown

Problem

wizard replay-vision ends on "Replay vision configured!" and a report path. Users whose run changed code on their machine do not learn that session replay records nothing until that change is deployed, so their scanners stay idle. The outro also gives no link to the scanners or to the replay setting.

Changes

  • The replay-vision outro shows next steps: deploy any code the run changed, check that "Record user sessions" is on (link to the project's replay settings), and see the scanners (link to Replay Vision in the run's project).
  • createSkillProgram passes buildOutroNextSteps through, so an orchestrated skill program can add outro bullets.

Why: the deploy is the step that starts the scanners, and users need to see it at the end of the run.

Related: PostHog/context-mill#448 (report leads with replay-off and deploy warnings) and PostHog/context-mill#449 (scanner queries checked against real sessions).

Test plan

  • pnpm build, pnpm typecheck pass.
  • vitest run src/programs/replay-vision src/programs/program-runner: 100 passed, including a new test for the outro links.

LLM context

Written with Claude Code from a review of wizard-created Replay Vision scanners that are enabled but produce no observations.


🤖 Generated with Claude Code

The replay-vision outro lists next steps: deploy any code the run changed, check that "Record user sessions" is on, and open the scanners. createSkillProgram passes buildOutroNextSteps through, so an orchestrated skill program can add outro bullets.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Generated-By: PostHog Desktop
Task-Id: 158f9145-6821-4694-9719-574ec121ec75
@ksvat ksvat self-assigned this Oct 30, 2026
@github-actions

Copy link
Copy Markdown

🧙 Wizard CI

Run 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:

  • /wizard-ci all

Test all apps in a directory:

  • /wizard-ci ai-observability
  • /wizard-ci basic-integration
  • /wizard-ci feature-flags
  • /wizard-ci mcp-analytics
  • /wizard-ci replay-vision
  • /wizard-ci revenue
  • /wizard-ci self-driving
  • /wizard-ci warehouse
  • /wizard-ci warehouse-seeded

Test an individual app:

  • /wizard-ci ai-observability/anthropic
  • /wizard-ci ai-observability/google-adk
  • /wizard-ci ai-observability/groq
Show more apps
  • /wizard-ci ai-observability/manual-capture
  • /wizard-ci ai-observability/openai
  • /wizard-ci ai-observability/openai-agents
  • /wizard-ci ai-observability/opentelemetry
  • /wizard-ci ai-observability/vercel-ai
  • /wizard-ci basic-integration/android
  • /wizard-ci basic-integration/angular
  • /wizard-ci basic-integration/astro
  • /wizard-ci basic-integration/django
  • /wizard-ci basic-integration/fastapi
  • /wizard-ci basic-integration/flask
  • /wizard-ci basic-integration/flutter
  • /wizard-ci basic-integration/javascript-node
  • /wizard-ci basic-integration/javascript-web
  • /wizard-ci basic-integration/laravel
  • /wizard-ci basic-integration/next-js
  • /wizard-ci basic-integration/nuxt
  • /wizard-ci basic-integration/python
  • /wizard-ci basic-integration/rails
  • /wizard-ci basic-integration/react-native
  • /wizard-ci basic-integration/react-router
  • /wizard-ci basic-integration/sveltekit
  • /wizard-ci basic-integration/swift
  • /wizard-ci basic-integration/tanstack-router
  • /wizard-ci basic-integration/tanstack-start
  • /wizard-ci basic-integration/vue
  • /wizard-ci feature-flags/django
  • /wizard-ci feature-flags/next-js
  • /wizard-ci mcp-analytics/custom-dispatcher
  • /wizard-ci mcp-analytics/typescript-sdk
  • /wizard-ci replay-vision/javascript-node
  • /wizard-ci replay-vision/next-js
  • /wizard-ci replay-vision/react-vite
  • /wizard-ci revenue/stripe
  • /wizard-ci self-driving/astro
  • /wizard-ci self-driving/fastapi
  • /wizard-ci self-driving/nuxt
  • /wizard-ci self-driving/react-router
  • /wizard-ci self-driving/sveltekit
  • /wizard-ci warehouse/monorepo-env
  • /wizard-ci warehouse/multi-source-next
  • /wizard-ci warehouse/stripe-node
  • /wizard-ci warehouse/zero-source
  • /wizard-ci warehouse-seeded/next-stripe
  • /wizard-ci warehouse-seeded/next-stripe-declined

Test against a Context Mill branch:

  • /wizard-ci all context-mill:my-branch

Add context-mill:<branch> to any command above to pin the Context Mill branch. It defaults to main.

Results will be posted here when complete.

@ksvat
ksvat marked this pull request as ready for review October 30, 2026 21:48
@ksvat
ksvat requested review from a team as code owners October 30, 2026 21:48
@ksvat
ksvat requested review from TueHaulund and fasyy612 and removed request for a team October 30, 2026 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants