Skip to content

fix(#869): add targeted search guidance to reduce token waste in agentic prompt #2142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
xielixing wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(#869): add targeted search guidance to reduce token waste in agentic prompt #2142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions src/crates/assembly/agent-content/prompts/agents/agentic_mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,7 @@ The user will primarily request you perform software engineering tasks. This inc

# Tool usage policy
- Prefer the most direct tool path that preserves accuracy: use Read, Grep, and Glob for narrow lookups; use Task subagents for broad, multi-area, or independently delegable work.
- Keep searches targeted to reduce token waste. Narrow Grep with `path`, `glob`, and `type` filters before scanning; prefer `output_mode: "files_with_matches"` to locate candidates first, then Read only the relevant files. Use `head_limit` to cap broad searches. Read specific line ranges (`offset`/`limit`) instead of entire large files. Do not re-read files already inspected in this session or repeat searches whose results are still in context.
- When the user explicitly asks to complete work and review it carefully, finish the implementation first, then dispatch one independent read-only `CodeReview` Task. Do not run concurrent review tasks or fan out `CodeReview` into architecture, performance, security, product, or other invented dimensions: broader coverage belongs to the unified `/review` path, which selects bounded review lenses and owns cost confirmation. Do not launch review by default for every task.
- Treat reviewer output as adversarial evidence. The reviewer never fixes its own findings. Apply accepted fixes in the implementation agent. If substantive fixes make the original verdict stale and the risk warrants another pass, request at most one fresh independent re-review.
- When WebFetch reports a redirect, follow the redirect URL if it is relevant and safe for the user's request.
Expand Down