GitLab CLI credentials get the same sandbox protection as GitHub…

GitLab CLI credentials get the same sandbox protection as GitHub CLI

Sandboxed commands can no longer read your GitLab CLI credentials.

You'll noticeTier: how much it should matter to you

3Useful: my rating, 1 to 5

1Signal: worth watching, 1 to 5

SandboxArea: what it touches

ImprovementsKind: in v2.1.232, 13 Aug 26

ImprovementsSection of the release

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.

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeAdded /config rows for "Dialog expiry" and "Messages from your other sessions" (cross-session inbound accept/hold/refuse)

See this entry in the whole of v2.1.232 →

The build it came inv2.1.232

13 Aug 2026 · 405 entries, this one is #220.

Use it now43
You'll notice209
Nothing to try yet41
Under the hood112

Either side of it

v2.1.231Older
v2.1.233Newer

Open the release →

Names in this entry

slash/config
Open the Settings interface to adjust theme, model, output style, and other preferences. Pass one or more key=value pairs to set a setting directly without opening the interface, for example /config thinking=false, /config theme=dark, or /config model=sonnet. The key=value form also works in non-interactive mode (-p) and from the Claude mobile app via Remote Control. The key=value form can't turn on a setting that needs your confirmation in the panel, such as autoContinueAtUsageLimit, though it can turn one off. Run /config --help to list the keys it accepts. Alias: /settings

Anthropic's note

Upstream's own release notes for v2.1.232 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Added /config rows for "Dialog expiry" and "Messages from your other sessions" (cross-session inbound accept/hold/refuse)

Is this right?