How we solved Context Management in Agents — Sally-Ann Delucia

An agent can keep a shorter active conversation without permanently discarding the material it removes. Arize's account of its Alex agent describes retaining previews from the beginning and end of older material while storing the omitted content for later retrieval. Database identifiers let the agent request that content again when a follow-up needs it.

This changes truncation from irreversible loss into selective access. The team also tests delayed failures by loading ten conversation turns and evaluating the eleventh. The account concerns managing information within conversations; memory across separate chats was still being developed at the time of the talk.

“the best context strategy is one that lets your agents remember what it needs to um, and forget what it doesn't”

Sally-Ann Delucia

“context management isn't is a product and a UX problem, not just an engineering one”

Sally-Ann Delucia

“the main takeaway from this was that over truncation had broke the reasoning. It couldn't remember.”

Sally-Ann Delucia

“We were kind of hoping to get a little bit of a a secret from from them, but I guess we'll all just have to keep you know, doing our own research there.”

Sally-Ann Delucia

“agents don't fail because of prompts, they fail because of context”

Sally-Ann Delucia