-
Notifications
You must be signed in to change notification settings - Fork 47
Closed
4 / 44 of 4 issues completedClosed
4 / 44 of 4 issues completed
Copy link
Labels
Description
Overview
This tracking issue covers the implementation of conditional cache memory updates based on detection results in agentic workflows.
Source: Issue #5760
Problem
Currently, cache memories are updated unconditionally at the end of agentic jobs. This can be problematic when detection finds threats, as we don't want to persist potentially compromised memory states.
Solution
Implement a detection-aware cache update mechanism:
- Agentic jobs upload memories as artifacts (not cache updates)
- Detection jobs conditionally update cache based on threat detection
- Handle the case when detection is disabled
Planned Tasks
- Modify agentic job to upload memories as artifacts - Change the memory persistence logic to use artifacts instead of cache updates
- Update detection job to handle memory artifacts - Download both cache and artifacts, conditionally update cache
- Handle detection-disabled case - Update cache directly in agent job when detection is disabled
- Update workflow compiler logic - Ensure compiler generates correct job dependencies and artifact handling
Acceptance Criteria
- Memories are uploaded as artifacts in agentic jobs (not updated early)
- Detection job downloads cache memory and memory artifacts
- Cache is only updated if detection finds no threats
- When detection is disabled, cache updates happen in agent job
- All existing workflows continue to function correctly
Related to Cache update #5760
AI generated by Plan Command for #5760
Reactions are currently unavailable