Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.206 Home All releases ←olderv2.1.205 v2.1.207newer→
Claude Code v2.1.206

Dynamic Git Remote Detection for Push Permissions

What

Permission rules for git push now automatically include the repo's configured push remote, not just origin.

Details
  • Before adding a Bash(git push origin *) rule, Claude now queries git config remote.pushDefault to find the actual configured push target.
  • If only one remote is configured, it is used regardless of name.
  • The resolved remote is added alongside origin in the allowed-patterns list, so both git push origin and git push {remote} are permitted.
  • This prevents unnecessary permission prompts for repos that push to upstream, a fork remote, or any non-origin name.
Evidence

Remote resolution (search for "remote.pushDefault"); dynamic rules (search for "git push -u" alongside "rwn")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.206 →