What
A permission mode controls how much Claude may do without asking you first. When you start a cloud session, Claude Code decides its model and permission mode. That decision now takes more into account:
- The message about permission modes in cloud sessions now says a cloud session does not inherit a permission mode and that
--permission-modesets it. Before, it said the mode came from the repository's settings. - The decision now receives
typedLevelandcarriedMode, so the level you typed and the mode carried over from where you started are considered. - A new source of the chosen mode,
default_auto, covers sessions that start in auto mode by default. Before, the only recorded sources wereauto_seeded,flag,settingsandnone. - An extra notice is shown when a session is created or attached to.
- Tools served to the session get a
needsOwnFlagAnsweroption.
The related gate tengu_remote_model_gate_hint has not been read, so whether these paths are active for any given account is unknown.
Why
If you start cloud sessions, the mode they begin in now depends on the flag you pass rather than on repository settings, and some sessions may begin in auto mode. Passing --permission-mode is the way to choose it.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear how the carried mode and typed level change the choice, or what the second notice says.