Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Auto mode's user-boundary rule can now cover commits in connected apps

Auto mode's safety check has a second version of its user-boundary rule that also covers committing changes in a connected app or account

You'll notice Improvements
JSON All of v2.1.284
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Auto ModeArea: what it touches
ImprovementsKind: in v2.1.284,
ImprovementsSection of the release
What

In 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.

That rule used to be a single fixed sentence. It now comes in two versions:

  • One keeps the original wording.
  • 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.

The 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.

Why

Where 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which part of Claude Code uses the version that covers connected apps.

See this entry in the whole of v2.1.284 →

Feedback