fix: Don't stop analytics after integration run inside self-driving#771
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. |
There was a problem hiding this comment.
Pull request overview
This PR adjusts the agent runner so that when the PostHog integration is executed as a composed sub-run inside the self-driving program, it does not run a terminal outro or shut down the shared analytics client—allowing analytics to continue for the remainder of the host run.
Changes:
- Runs the integration agent with a new
{ composed: true }option when invoked as a composed step inside self-driving. - Threads the
composedoption through the unified runner into the linear pipeline. - Skips the linear pipeline’s outro +
analytics.shutdown('success')whencomposedis enabled.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/lib/programs/posthog-integration/index.ts | Marks the composed integration run step to invoke the agent runner with { composed: true }. |
| src/lib/agent/runner/linear.ts | Adds a composed flag and returns before outro + analytics shutdown for composed sub-runs. |
| src/lib/agent/runner/index.ts | Threads composed options into the runner so the linear pipeline can skip outro + analytics shutdown. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| if (isOrchestratorEnabled(boot.wizardFlags)) { | ||
| getUI().log.info('Task-queue orchestrator enabled.'); | ||
| stampVariant(boot, WizardVariant.ORCHESTRATOR); | ||
| // composed-run guard is linear-only; the orchestrator is experimental. | ||
| return await runOrchestrator(session, programConfig, boot); | ||
| } |
Problem
analyticsbefore jumping to self-drivingChanges
Test plan