Closed
feat(scout): add depth parameter for controlling research thoroughness#17116
depth parameter for controlling research thoroughness#17116Conversation
- Add `depth` input (1-5, default: 3) to workflow_dispatch inputs - Update prompt to parse depth from slash command text (e.g. /scout depth=5) - Define depth levels: 1=quick scan, 2=light, 3=standard, 4=deep, 5=exhaustive - Scale research thoroughness (searches per tool) based on depth - Recompile scout.lock.yml Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add depth parameter to scout agent slash command
feat(scout): add Feb 20, 2026
depth parameter for controlling research thoroughness
Collaborator
|
@copilot No depth means how to clone (0=shallow), but also allow full history, etc. |
…depth convention - Add `0` as a valid depth value (full/unlimited research, like fetch-depth: 0) - Rename depth=1 from "Quick scan" to "Shallow" to match git shallow clone terminology - Update frontmatter description to document the 0=full/unlimited convention - Update examples in Mission section to show depth=0 - Recompile scout.lock.yml Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Contributor
Author
Good catch. Updated in 87f70d5 — Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Collaborator
|
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.
The
/scoutslash command had no way to control how deeply the agent investigates a topic — every invocation used the same fixed research effort regardless of complexity.Changes
workflow_dispatchinput: Newdepthfield (0–5, default3) for manual triggersdepth=Ninline from comment text (e.g./scout depth=5or/scout depth=0for full research)3)fetch-depthconvention (0= full/unlimited,1= shallow):0– Full research: no limit on searches, exhaustive cross-referencing (likefetch-depth: 0= full history)1– Shallow: 1–2 searches/tool, surface-level findings only2– Light: 2–3 searches/tool, basic cross-referencing3– Standard: 3–5 searches/tool, balanced depth and breadth4– Deep: 5–8 searches/tool with extended follow-up5– Exhaustive: 8+ searches, maximum cross-referencingExample
Triggers full/unlimited research mode — no cap on searches, exhaustive cross-referencing across Tavily, DeepWiki, arXiv, and Microsoft Docs.
Triggers exhaustive research mode — 8+ searches per tool with full cross-referencing across Tavily, DeepWiki, arXiv, and Microsoft Docs.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.