What
Two new instructions tell the model that your CLAUDE.md, permission rules and preferences were sent from your machine but either had not been applied when the turn started, or could not be taken at all, and that it must tell you rather than acting as if they were in effect. So a cloud session running on defaults now says so instead of silently ignoring your rules.
Details
- The two cases are distinct: settings in flight but not yet applied at the start of the turn, and settings that the session could not take, in which case it runs on its default settings.
- The strings sit next to the timing constants for settings sync, so they apply to sessions that use that sync path.
- No flag guards the definitions themselves.
Evidence
but this session could not take it, so it runs on its default settings
Strings lifted out of the shipped bundle, so the claim above can be checked against them.