fix(self-driving): Say that it opens PRs on its own - #1025
Closed
Twixes wants to merge 1 commit into
Closed
Conversation
Ticket #65283: a user picked Linear from the step-5 multi-select reading it as "which tools do you use?", and woke up to 14 unrequested PRs and a $345 bill against issues they'd filed as their own future work. Autostart is on by default at every priority and runs as whoever enabled the sources, but nothing in the run said so — and the outro/learn deck actively framed the PR as something you kick off yourself. No behavior change, disclosure only.
🧙 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. |
Contributor
Author
|
Consolidating into PostHog/context-mill#292 — the step-5 question text lives entirely in the skill, so one repo can carry this. Not worth a wizard release too. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Support ticket #65283. A user picked Linear from the step-5 multi-select — which asked "Which of these do you use?" with bare labels — and woke up to 14 unrequested PRs and a $345 bill, against issues they'd filed as their own future work.
Autostart is on by default at every priority (
autostart_enabledis nullable, only explicitFalsedisables it;default_autostart_priority= P4), and when no reviewer resolves it runs as whoever enabled the sources — i.e. whoever ran the wizard. The backend's own docstring says "enabling a signal source is the team's opt-in to the signals product, of which autonomous PRs are a part." We never earned that opt-in.Worse than the silence: the outro said "Kick off a PR when you like the proposed fix" and the learn deck "tag teammates, or kick off a PR" — both frame the PR as a pull, contradicting the default.
Changes
Disclosure only, no behavior change. One dimmed line per option, no new questions — onboarding stays fast.
prompt.ts: step 5's wording is verbatim, never reduce an option to a bare tool nameARCHITECTURE.md§10: the disclosure contract + the two traps (optiondescriptionrenders in the multi path only; pull-framing is worse than silence)Paired with PostHog/context-mill#TBD, which does the load-bearing half — the per-option descriptions on the step-5 ask and the mandatory report section. That ships independently of the npm release, and can go first safely (the
descriptionfield already exists in shipped wizards).Test plan
pnpm build && pnpm test && pnpm fix— 1540 pass, lint clean. Copy-only otherwise.LLM context
Written with Claude Code. Ticket traced through
products/signals/backend/auto_start.py(maybe_autostart_implementation_task,_resolve_autostart_fallback_user) andSignalTeamConfigdefaults to confirm the behavior before touching copy.