The agent couldn't click Allow

The other day I started to notice a pattern. My coding sessions kept getting stuck. No obvious errors, just stuck. I’d leave my coding session going when I went out for the day, I’d turn on remote mode, and I’d see that it would get stuck and misbehave in some way or not be able to do what I was asking. It was really weird. After a few days trying various fixes, like splitting the jobs into smaller chunks, I put two and two together: whenever this would happen, I’d come home and find my Mac prompting me to allow Claude access to a folder. And then it clicked… somehow Claude needed access and then wasn’t able to do what it had planned, and my session would start misbehaving. What was happening? The first thing any session does as part of Agent M is read its memory vault (a local storage directory). That folder needed permission. When I’m there, I click Allow without thinking about it. But a lot of the time I wasn’t there. Granting broader folder access made the prompts go away, not a perfect solution, but better. So today I learned that when something gets stuck for days, it’s worth asking what it was waiting for.