fix(self-driving): create custom scouts with scout-create, not skill-create - #411
Merged
andrewm4894 merged 1 commit intoSep 25, 2026
Conversation
…create Step 6b told the wizard to create each approved scout with `skill-create`. That call does not grant the report-channel tools, so the new scout ran on the deprecated signal channel and sent weak findings for later clustering instead of writing full inbox reports. Switch the recipe to `scout-create`, which grants the report tools and writes the config in one atomic call. Also correct the name rule: the `signals-scout-` prefix only drives config auto-registration, which `scout-create` does itself, so the prefix is a readability choice and not a run requirement. Generated-By: PostHog Desktop Task-Id: b0c568e1-a021-4e49-8085-c9c1fcafd73e
🧙 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
Test against a wizard branch:
Add Results will be posted here when complete. |
andrewm4894
marked this pull request as ready for review
September 25, 2026 15:38
andrewm4894
approved these changes
Sep 25, 2026
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
skill-create. That call does not grant the report-channel tools, and the scout prompt turns the report channel on only whenemit_report/edit_reportare stored.signals-scout-prefix mandatory. The prefix only drives config auto-registration, so a valid name without it is still runnable when the config is created alongside the skill.Origin
Changes
scout-create. It grants the report-channel tools and writes the skill and its config in one atomic call, which is what makes the first run land on the report channel.skill-create(before)scout-create(after)signals-scout-*globsignals-scout-config: {"enabled": true}and nothing else, so the posture the wizard intends is explicit whileemitandrun_interval_minutesstay the server's defaults.signals-scout-<scope>as a deliberate naming choice for a readable troop, not a run requirement.description.mdto match.Agent context
scout-createschema and the currentauthoring-scoutsguide, not from the report alone.npm test(215 tests) andnpm run buildboth pass.Created with PostHog Desktop from this inbox report.
🤖 Generated with Claude Code