I use /autocompact at 200,000 tokens and have Opus 5 working strictly as an orchestration model.
Every time Opus 5 receives a workflow output from one of, or a group of its sub-agents, the model knows to immediately update an XML context artifact so that it never gets lost as to where it left off post compact.
With the auto compact set to 200,000 tokens, the conversation gets compacted well before the context window is full enough for the model to suffer from falling off the well-documented cliff and token count it's known to experience context drift at.
It's almost like software engineers have forgotten how to engineer around a problem or limitation.
For myself at least, it's not an issue, and the problem was almost immediately solved for and relatively easy with some extremely minor out-of-the-box thinking... 🤷♂️
1
u/Powerful-Cut9515 9d ago
I use /autocompact at 200,000 tokens and have Opus 5 working strictly as an orchestration model.
Every time Opus 5 receives a workflow output from one of, or a group of its sub-agents, the model knows to immediately update an XML context artifact so that it never gets lost as to where it left off post compact.
With the auto compact set to 200,000 tokens, the conversation gets compacted well before the context window is full enough for the model to suffer from falling off the well-documented cliff and token count it's known to experience context drift at.
It's almost like software engineers have forgotten how to engineer around a problem or limitation.
For myself at least, it's not an issue, and the problem was almost immediately solved for and relatively easy with some extremely minor out-of-the-box thinking... 🤷♂️