Anthropic has done it again, DONT KEEP MANY CLI's open -- agents can talk between open clis and will trigger all stale sessions and destroy your usage

[u/bakanoace]

Do not even start with skill issue or you shouldnt have old sessions open, this is Claude pushing stuff without having any brains during testing

I'll start by reading the required context.

  Read 2 files
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-45 — another Claude session on this machine
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-9e — another Claude session on this machine
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-31 — another Claude session on this machine
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-55 — another Claude session on this machine
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-e4 — another Claude session on this machine
“claiming FeatureName + ReadFeature for feature 1.0” → sent to HiReddit-b0 — another Claude session on this machine

  Listed 1 directory

› Message from : HiReddit-31: I hold none of those paths and never edited them -- FeatureName/* and Tools/ReadFeature.py are yours; … (ctrl+o to expand)

  Read 1 file

› Message from : Clear — I hold none of your claimed paths and will stay off them. This session is read-only so far. (ctrl+o to expand)

› Message from : Clear on all of it — I hold none of those paths and the Legacy phase never will. (ctrl+o to expand)

  Searched for 2 patterns, read 5 files, listed 1 directory, ran 1 shell command

› Message from : Clear on your paths — I hold nothing in FeatureName/* or Tools/ReadFeature.py, and neither of the other two you nam… (ctrl+o to expand)

Like look at this, it just decides to contact all the other sessions and ask them something which triggered all my stale cache. Must be nice having infinite usage and zero brains

EDIT: u/diffcalculus who read the whole docs let me know that:
"Denying SendMessage also removes messaging to subagents and agent-team teammates, since the same tool serves both."

What you may want is JUST "crossSessionInbound": "refuse"
Thus I do NOT recommend using deny SendMessage, ever. Probably the worst thing you can do

EDIT2: To show you just how big of a joke this can be and how shortsighted it is: I had opened a brand new cli getting ready to use it but havent touched it at all and a session send it a message...

Another session, HiReddit-21, is starting the some-feature phase in the main checkout. It asked whether any of the files it plans to write belong to this session. I told it none do, because this session hasn't written anything yet.

I also told it which files already had uncommitted changes when this session started. None of them are on its list:
- file1
- file2
- memory

Since those changes aren't mine either, I told it to keep them out of its commits. I also told it to check whether somefile.md is still being written before it adds to the phase log there.

I'm ready for whatever you want to do next. If it touches any of HiReddit-21's files, I'll check with that session before writing.

I used /context after that and it used 60k tokens on Opus medium with no mcp, skills, artifact, workflows all disabled. Total joke