docs(design): context management design document #546
docs(design): context management design document #546dbschmigelski wants to merge 2 commits intostrands-agents:mainfrom
Conversation
dbschmigelski
changed the title
Documentation Deployment CompleteYour documentation preview has been successfully deployed! Preview URL: https://d3ehv1nix5p99z.cloudfront.net/pr-546/ |
|
/strands review |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Assessment: Comment This is a well-researched design document that provides a thoughtful strategic direction for context management in Strands Agents. The document effectively synthesizes academic research (MemGPT, Recursive Language Models) with practical industry examples and aligns well with SDK tenets. Review Summary
The design principles, research foundations, and prioritized work plan are well-articulated. 👍 |
designs/0003-context-management.md
Outdated
| 6. Proactive context compression M Medium — Most requested context feature (#555). Depends on: 2, 3 | ||
| 7. In-event-loop context management M Medium — Manage context within a cycle for tool-heavy agents (#298) | ||
| 8. Semantic dynamic tool registry XL Medium — Needs design doc + vector store integration (#1677) | ||
| 9. Large content aliasing M Low — Externalize oversized results so agents navigate on demand instead of inlining (#1678). Depends on: 5 |
There was a problem hiding this comment.
It definitely was inspired by it and of course they are highly related.
The way I view it is similar to how we are doing Retries. I want customers to be able to handle this themselves [hook]. But, the framework will also provide an opinionated solution [alias]
Make sense?
|
|
||
| --- | ||
|
|
||
| ## Work Plan |
There was a problem hiding this comment.
This would present better as a table FYI
|
Noting that |
- Fix missing period in overview paragraph - Add heading markers for Dynamic Tool Loading and Autonomous Approach - Separate Autonomous Approach heading from inline paragraph content - Update "Hooks" to "Plugins" in Design Principle #1 - Convert work plan from numbered list to table format - Move Autonomous delegation meta-tool up in priority (standalone, customer-requested) - Update Context navigation meta-tools size from L to S
dbschmigelski
temporarily deployed
to
auto-approve
GitHub Actions
Inactive
Documentation Deployment CompleteYour documentation preview has been successfully deployed! Preview URL: https://d3ehv1nix5p99z.cloudfront.net/pr-546/ |
3 participants
This PR introduces a design document that explores how we can improve context management in Strands Agents.
Today, when conversations grow long or tool results get large, our options are limited: sliding window drops messages permanently, summarization loses detail over time, and there's no way to retrieve content once it leaves the active window.
This document lays out a direction for doing better, organized around three tracks: making conversation context recoverable instead of permanently lost, reducing the overhead of tool definitions that get sent with every request regardless of relevance, and giving agents the ability to delegate work to keep their own context window clean.
The ideas draw from research like MemGPT and Recursive Language Models, and the document is meant to guide the work ahead, individual features will get their own design docs as we go. The goal is to agree on the problems that should be solved and the mechanism that can solve them, without focussing on exact syntax.