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.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

GitLab CLI credentials get the same sandbox protection as GitHub CLI

You'll notice
Useful3 Signal1
Sandbox

Sandboxed commands can no longer read your GitLab CLI credentials.

What

Sandboxed commands are now blocked from reading GitLab CLI credentials the way GitHub CLI ones already were.

Details
  • .config/glab-cli is created and scrubbed in the home directory alongside .config/gh, and .git/glab-cli is removed by the git-scrub paths (four call sites).
  • The regex that flags a read as touching credentials now matches .config/glab-cli/config.yml next to .config/gh/hosts.yml.
Evidence

glab-cli, .config\/glab-cli\/config\.yml\b

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →