Question about making Full Access the default permission mode

[uiharuayako]

@bobleer
Hi, I’d like to better understand the reasoning behind PR #3002, which changes the default tool permission mode from Ask to Full Access.
Could the author share what motivated this change? Was the goal to reduce approval interruptions or preserve the experience of the earlier automatic tool execution behavior?
I have some concerns about the security implications for first-time users. With Full Access enabled by default, users may begin using the agent without realizing that file changes and command execution can proceed without individual approval. Missing permission settings in an existing configuration also appear to inherit this default.
I understand that project and enforced restrictions still apply. However, users with a fresh installation may not have configured additional restrictions yet. I also noticed that manually switching to Full Access requires a warning confirmation, while the initial default does not go through that confirmation.
Would it be worth considering Ask as the default, or offering an explicit permission-mode choice during initial setup?
I may be missing some context, so I’d appreciate clarification on the intended user experience and the security tradeoffs considered here.