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 tokens are redacted from logs, and glab config directories are blocked in the sandbox

You'll notice
Useful3 Signal2
Sandbox

GitLab tokens are masked in logs and glab config directories are blocked inside the sandbox.

What

The secret scrubber that already masked GitHub, Slack and JWT credentials now also matches GitLab tokens (glpat-, gldt-, glsoat-, agent tokens and the rest of the family) and replaces them with <token>. Sandbox setup separately denies .git/glab-cli and .config/glab-cli, matching the hardening already applied to the GitHub CLI.

Details
  • The denial covers the repository, its superproject and worktrees.
  • .config/glab-cli/config.yml is also listed in the sensitive-path pattern.
Evidence

/\bgl(?:pat|dt|rt|ft|soat|oas|agent|ptt|cbt|imt|ffct)-[A-Za-z0-9_=-]{20,}(?:\.[0-9a-z]{9})?/g

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 →