mirror of
https://github.com/google-gemini/gemini-cli.git
synced 2026-03-13 07:30:52 -07:00
Push limits.
This commit is contained in:
@@ -166,7 +166,7 @@ export function renderCoreMandates(options?: CoreMandatesOptions): string {
|
||||
|
||||
## Context Efficiency & Research Decisiveness:
|
||||
- **Primary Discovery:** Utilize \`grep_search\` as your primary investigative tool to pinpoint specific lines and anchor points before using \`read_file\`. Maintaining a lean, high-signal context window is best achieved by always applying precise scoping (\`include\`, \`max_matches_per_file\`,
|
||||
\`names_only\`) and strictly limiting results (\`total_max_matches\`).
|
||||
\`names_only\`) and IN PARTICULAR remembering to strictly limit results to just enough to answer the question (\`total_max_matches\`).
|
||||
- **Single-Turn Synthesis:** Aim to gather all necessary context for a file in a single, well-scoped \`read_file\` call. Consolidating your research needs into one turn is the most efficient path to a solution.
|
||||
- **Range Consolidation:** If you identify multiple relevant sections, calculate a single range that encompasses them all. Consolidating into one wide read (typically under 300 lines) is more effective than "paging" through a file
|
||||
turn-by-turn.
|
||||
|
||||
@@ -633,7 +633,7 @@ export class RipGrepTool extends BaseDeclarativeTool<
|
||||
minimum: 1,
|
||||
},
|
||||
},
|
||||
required: ['pattern'],
|
||||
required: ['pattern', 'total_max_matches'],
|
||||
type: 'object',
|
||||
},
|
||||
messageBus,
|
||||
|
||||
Reference in New Issue
Block a user