{"version":"2.1.284","anchor":"auto-mode-classifiers-bound-rule-now-varies-by-prompt-var","canonical_anchor":"auto-mode-classifiers-bound-rule-now-varies-by-prompt-var","heading":"Auto mode's user-boundary rule can now cover commits in connected apps","tier":"notice","area":"Auto Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/auto-mode-classifiers-bound-rule-now-varies-by-prompt-var","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Auto mode's user-boundary rule can now cover commits in connected apps\n\nAuto mode's safety check has a second version of its user-boundary rule that also covers committing changes in a connected app or account\n\n**Unclear.** It is not clear which part of Claude Code uses the version that covers connected apps.\n\n**What**\n\nIn auto mode, Claude Code runs a classifier: a check that decides whether an action Claude wants to take may go ahead without asking you. One of its rules says that when you have set an explicit limit, such as \"don't deploy\", an action crossing that limit is blocked.\n\nThat rule used to be a single fixed sentence. It now comes in two versions:\n\n- One keeps the original wording.\n\n- The other adds commits in a connected app or account to the list of actions this rule can block, alongside things like credentials and deploys.\n\nThe labels the classifier uses to tag a blocked action also gain two new categories. One covers changes to account standing rules. The other covers commits in a connected app that you did not ask for.\n\n**Why**\n\nWhere the second version applies, a limit you set, such as \"don't send\", now also counts for actions inside connected apps. Before, those actions were not on the list this rule could block.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}