fix: Say that Self-driving opens a PR per issue - #292
Merged
Conversation
Twixes
force-pushed
the
fix/self-driving-disclose-autonomous-prs
branch
from
July 29, 2026 15:56
d25841e to
ebbaf71
Compare
Twixes
force-pushed
the
fix/self-driving-disclose-autonomous-prs
branch
4 times, most recently
from
July 30, 2026 12:43
734aaeb to
8a0737e
Compare
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. Each option now carries its billing unit, taken from the tool's register_signal_source line in posthog's emission registry — so Shortcut says "per story", Plain "per thread", Raygun "per error group", rather than everything flattening to "per issue". In the label, not a description, which keeps the list one line per row and the prompt one line total. Framed as "automatically opens a draft PR" rather than "no approval step": same behaviour, but the negative framing reads as bypassing review to anyone at a larger org, when it's a draft that still goes through their normal review and CI. Google Search Console gets no unit: it has no emitter registered, so nothing it syncs bills.
Twixes
force-pushed
the
fix/self-driving-disclose-autonomous-prs
branch
from
July 30, 2026 12:54
8a0737e to
4f41727
Compare
andrewm4894
approved these changes
Jul 30, 2026
sortafreel
approved these changes
Jul 30, 2026
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
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.
Description by Claude, by I think quite good here:
Problem
Support ticket #65283. The step-5 ask asked "Which of these do you use?" over a list of bare tool names. A user read that as a question about their tooling, picked Linear, and woke up to 14 unrequested PRs and a $345 bill — against issues they'd filed as future work for themselves.
Autostart is on by default at every priority (
autostart_enabledis nullable, only explicitFalsedisables it;default_autostart_priority= P4) and runs as whoever enabled the sources. So this ask is the consent, and it never said what it was consenting to — least of all the unit it bills on.Changes
The unit goes in the label, so the prompt stays one line:
…and behind "Show more", the rest of the catalog with the same treatment —
Shortcut (per story),Raygun (per error group),Plain (per thread),Rapid7 InsightVM (per vulnerability),Productboard (per note), and so on.The units aren't category guesses — each is the table that tool's emitter actually reads, off its
register_signal_source(<source>, "<table>", …)line inproducts/signals/backend/emission/registry.py. That's why Shortcut bills per story and Raygun per error group instead of everything flattening to "per issue". All 36 cross-checked against the registry, applied to both asks.Skill-only on purpose: the question text lives here, so this needs no wizard release.
Needs the
mcp-publishlabel.Test plan
pnpm build—self-driving-setup.ziprenders. Units diffed line-by-line againstregistry.py. Copy-only otherwise.