My Claude Cowork inbox triage reads a fresh task file every run.
No memory of yesterday, by design,
so the reports never drift.
This week, that design had a cost.
Two calendar items looked like accidental duplicates.
- One was two event registration links landing as separate calendar entries.
- The other was two client meetings back to back, one of them titled PLACEHOLDER.
I confirmed both, in chat: stating, "all four were real, nothing to merge or delete."
The next morning, the same two questions came back. Same wording. As if I'd never answered.
The challenge was that if I gave it memory of the chats it would stop the repeat questions, but it would also break the fresh-read design that keeps the reports from drifting in the first place.
So the fix was simpler:
Write the confirmed exceptions into the task file itself, as a standing list it checks before asking anything.
How it works now, step by step:
- I confirm something, in chat, once
- That confirmation gets written into the task file as a standing exception
- Every future run checks that list first, before flagging anything
- If it matches, the item is reported as settled, not raised as a question
Cowork can:
โ๏ธ Read a fresh task file every run
โ๏ธ Check any exception already written into it
โ๏ธ Skip anything already settled
Cowork cannot:
โ Remember what I told it yesterday
โ Learn a new exception on its own