jcarr
/
gemini-cli
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

ensure system instruction also uses <state_snapshot> (#3951)

This commit is contained in:
Abhi 2025-07-12 02:15:56 -04:00 committed by GitHub
parent c9e194ec6a
commit 642d2e8d51
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
packages/core/src/core/prompts.ts
View File

@ -286,11 +286,11 @@ When the conversation history grows too large, you will be invoked to distill th
First, you will think through the entire history in a private <scratchpad>. Review the user's overall goal, the agent's actions, tool outputs, file modifications, and any unresolved questions. Identify every piece of information that is essential for future actions.
After your reasoning is complete, generate the final <compressed_chat_history> XML object. Be incredibly dense with information. Omit any irrelevant conversational filler.
After your reasoning is complete, generate the final <state_snapshot> XML object. Be incredibly dense with information. Omit any irrelevant conversational filler.
The structure MUST be as follows:
<compressed_chat_history>
<state_snapshot>
<overall_goal>
<!-- A single, concise sentence describing the user's high-level objective. -->
<!-- Example: "Refactor the authentication service to use a new JWT library." -->
@ -334,6 +334,6 @@ The structure MUST be as follows:
4. [TODO] Update tests to reflect the API change.
-->
</current_plan>
</compressed_chat_history>
</state_snapshot>
`.trim();
}