feat(self-driving): show codebase-detected tools first in the connected-tools ask - #291
Merged
Merged
Conversation
…ed-tools ask The step-5 connected-tools multi-select grew to ~36 options and overflows the terminal — the user can't see the whole list. Restructure the ask so it stays short: - The wizard now injects a "Tools detected in this codebase" block (a deterministic dependency + env-key scan). Step 5 puts those tools first. - Then the SaaS basics (GitHub Issues, Linear, Jira, Sentry, Zendesk), always offered. - Then a single "Something else…" option that expands to the full catalog in a second ask — only when the user asks for it. The default view drops from ~36 options to ~6-10. The connect / enable / record machinery (steps 2-5) is unchanged; only the ask construction moves. Degrades gracefully on an older wizard with no detected block — the list is still just the basics + "Something else…", and ordering falls back to step-2 evidence. Companion to the wizard change that emits the detected-tools block (PostHog/wizard#1022).
🧙 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. |
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
2 participants
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
The step-5 connected-tools multi-select grew from 5 → ~36 options (#254) and overflows the terminal — you can't see the whole list (thread). The fix agreed there: show the tools detected in the user's codebase first, then the SaaS basics, then an "others" bucket.
Changes
Restructures only the step-5 ask construction — the connect / enable / record machinery (steps 2–5) is untouched:
Default view drops from ~36 options to ~6–10.
Degradation
Safe without the wizard PR: with no detected block, the first ask is just the basics + "Something else…" (still a big improvement), and ordering falls back to the old step-2 evidence. So the two PRs are independent — either can land first.
Test plan
pnpm build(bundles theself-driving-setupskill) andpnpm test:skillsboth pass (285 skill tests). The change is a markdown reorder within one skill reference; no connector, source_type, or responder mapping changed.(Note:
pnpm security-scan:skillsfails locally with an unrelatedERR_MODULE_NOT_FOUNDin the scan tooling — an env gap on my machine, not this change. Worth a CI check.)