Skip to content

feat: iterating on summarize oneshot prompt #4113

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

Merged
katzdave merged 1 commit into from
Aug 15, 2025
Merged

feat: iterating on summarize oneshot prompt #4113

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
17 changes: 11 additions & 6 deletions crates/goose/src/prompts/summarize_oneshot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,27 +1,32 @@
## Summary Task
Generate detailed summary of conversation to date.
Include user requests, your responses, and all technical content.
## Task Context
- An llm context limit was reached when a user was in a working session with an agent (you)
- Generate a version of the below messages with only the most verbose parts removed
- Include user requests, your responses, all technical content, and as much of the original context as possible
- This will be used to let the user continue the working session
- Use framing and tone knowing the content will be read an agent (you) on a next exchange to allow for continuation of the session

**Conversation History:**
{{ messages }}

Wrap reasoning in `<analysis>` tags:
- Review conversation chronologically
- Review conversation chronologically
- For each part, log:
- User goals and requests
- Your method and solution
- Key decisions and designs
- File names, code, signatures, errors, fixes
- Highlight user feedback and revisions
- Confirm completeness and accuracy
- This summary will only be read by you so it is ok to make it much longer than a normal summary you would show to a human
- Do not exclude any information that might be important to continuing a session working with you

### Summary Must Include the Following Sections:
### Include the Following Sections:
1. **User Intent** – All goals and requests
2. **Technical Concepts** – All discussed tools, methods
3. **Files + Code** – Viewed/edited files, full code, change justifications
4. **Errors + Fixes** – Bugs, resolutions, user-driven changes
5. **Problem Solving** – Issues solved or in progress
6. **User Messages** – All user messages, exclude tool output
6. **User Messages** – All user messages including tool calls, but truncate long tool call arguments or results
Copy link
Collaborator

@katzdave katzdave Aug 15, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Notice any difference from this? I do think this has potential to help; seems like losing where you put a one-off script was one thing people were complaining about.

7. **Pending Tasks** – All unresolved user requests
8. **Current Work** – Active work at summary request time: filenames, code, alignment to latest instruction
9. **Next Step** – *Include only if* directly continues user instruction
Expand Down
Loading