Skip to content

fix: Say that Self-driving opens a PR per issue - #292

Merged
Twixes merged 1 commit into
mainfrom
fix/self-driving-disclose-autonomous-prs
Jul 30, 2026
Merged

fix: Say that Self-driving opens a PR per issue#292
Twixes merged 1 commit into
mainfrom
fix/self-driving-disclose-autonomous-prs

Conversation

@Twixes

@Twixes Twixes commented Jul 29, 2026

Copy link
Copy Markdown
Member

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_enabled is nullable, only explicit False disables 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:

Self-driving reads everything open in these and opens a draft PR for what it
can fix — no approval step, $15 each. Which do you use?

  ☐ None of these
  ☐ GitHub Issues (per issue)
  ☐ Linear (per issue)
  ☐ Jira (per issue)
  ☐ Sentry (per issue)
  ☐ Zendesk (per ticket)
  ☐ Show more (31 more hidden)

…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 in products/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-publish label.

Test plan

pnpm buildself-driving-setup.zip renders. Units diffed line-by-line against registry.py. Copy-only otherwise.

@Twixes
Twixes force-pushed the fix/self-driving-disclose-autonomous-prs branch from d25841e to ebbaf71 Compare July 29, 2026 15:56
@Twixes Twixes changed the title fix: Say that Self-driving opens PRs on its own fix: Say that Self-driving opens a PR per issue Jul 29, 2026
@Twixes
Twixes force-pushed the fix/self-driving-disclose-autonomous-prs branch 4 times, most recently from 734aaeb to 8a0737e Compare July 30, 2026 12:43
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
Twixes force-pushed the fix/self-driving-disclose-autonomous-prs branch from 8a0737e to 4f41727 Compare July 30, 2026 12:54
@Twixes
Twixes merged commit 3abb66a into main Jul 30, 2026
13 checks passed
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