feat: Add a redact agent #571
Conversation
This is not a full summarization, but instead slows down how quickly tokens accumulate by redacting recurring instances. We need to test this, it does mean the model cannot see all the changes that happened. However those should be redundant with other tool uses
Desktop App for this PRThe following build is available for testing: The app is signed and notarized for macOS. After downloading, unzip the file and drag the Goose.app to your Applications folder. This link is provided by nightly.link and will work even if you're not logged into GitHub. |
| // Map to track the last occurrence of each resource URI | ||
| let mut uri_last_index: HashMap<String, usize> = HashMap::new(); | ||
|
|
||
| // First pass: find all resource URIs and their last occurrence |
There was a problem hiding this comment.
nit: i think we can do this in one pass by iterating in reverse order
|
nice - wasn't familiar with this use of "redact" as a term, but could be good. I read correctly this means that the redaction shows earlier in the prompt (minor downside being cache loss?).
I wonder if longer term this doesn't matter too much, at least for code/text changes where with some future system it could use git staging/working commits and then ask it to look back in diff form? |
This is not a full summarization, but instead slows down how quickly tokens accumulate by redacting recurring resources. We need to test this, it does mean the model cannot see all the changes that happened. However those should be redundant with other tool uses