I run a few Claude Code sessions side by side: one for a work plugin, others for a small information site, data collection and video. I wrote the incidents down in a Korean ebook, and these are four of them, in short.
1. Two sessions edited the same file
Two sessions changed the same file, and a change I had not approved ended up deployed. Since then each session has a defined scope and owns specific files. Nothing else touches them.
2. A scheduled job failed quietly
A scheduled task hit a failure, swallowed it and moved on. I found out much later. A scheduled run now has to leave a record I can check, and a failure has to be visible rather than skipped.
3. The report said "checked", the number was wrong
A session reported that it had verified a figure from a regulation. It was wrong. I now keep a short definition of "done" and a verification step that does not rely on the session's own summary.
4. A generation job died on memory
A generation job kept retrying while memory was low and eventually died. For local generation models I now calculate the VRAM needs before starting.
What is still unsolved
These fixes reduce the problems, they do not remove them. Session coordination in particular still costs me attention, and I do not have a clean answer for it.
If you run multiple agent sessions, how do you split ownership of files and decide when a task is done?
The ebook is in Korean (PDF, 4,900 KRW): 혼자서 팀처럼 일하기 on BOOKK
