MEMTRACK
Fits engineering or project assistants that watch several work tools over time and must keep an accurate picture of what is true now. Borrow the time-ordered multi-platform timeline with planted conflicts and the correctness/efficiency/redundancy split.
What it asks the agent to do
- track the current state of a task across interleaved Slack, Linear and Git events
- resolve conflicting or outdated information from different platforms
- decide which earlier events matter for a question about the codebase or project
- explore a repository or file system to confirm a remembered fact
What to borrow from it
case templatesandbox design
Caveats
No public code or data link was found and the exact scoring procedure is not described in the abstract; task count unknown; workshop paper.
Details
| Workloads | memory, it ops, devops, coding |
|---|---|
| Interaction | multi turn scripted |
| Environment | mixed |
| End state checked | No |
| Tools | simulated chat, issue tracker, git and file system |
| Grading | llm judge, trajectory check |
| Size | Not published |
| Data | synthetic |
| Personal data | none |
| License | unknown |
| Harness | none |
| Status | active |