feat: Expose deep scan controls - #188
Merged
Merged
Conversation
daneschneider-oai
approved these changes
Jul 31, 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
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.
Expose deep-scan discovery controls in the CLI and TypeScript SDK so callers can set worker count, per-worker subagents, saturation, and the discovery-run limit.
Explicit settings override saved
[deep_scan]configuration and survive scan reruns. The bundled plugin now reuses the workbench scan already registered by the SDK instead of starting a second scan.Validated with SDK tests, package build and type checks, and a live single-worker scan that reproduced an HTTP path traversal and produced sealed, verified scan artifacts.