glab(1)

Reading the glab(1) manual, bestie? Then you're on the glab-cluster-agent-token-cache page, and it's all about managing cached GitLab Agent tokens. 💖✨

🎀 NAME 🎀

glab-cluster-agent-token-cache — manage cached GitLab Agent tokens. No cap, that's the vibe. 💅

🌸 SYNOPSIS 🌸

Run it like this, bestie:

glab cluster agent token-cache  [flags]

💅 DESCRIPTION 💅

Okay so here's the tea: tokens created by glab cluster agent get-token are cached locally in the system keyring and filesystem, so you don't have to create a new token for every single kubectl operation. Obsessed with efficiency, honestly. 💖

The GitLab CLI caches agent tokens in two locations:

• Keyring — uses the system keyring: Windows Credential Manager, macOS Keychain, Linux Secret Service. 🔐
• Filesystem — stores tokens in the user's cache directory as encrypted files. 🗂️

The cache improves performance by avoiding the need to create new tokens for each kubectl operation when using glab cluster agent update-kubeconfig. Literally such a glow-up for your workflow. ✨

Cached tokens are stored using a key format that includes:

• Base64-encoded GitLab instance URL
• Agent ID

This ensures tokens are properly isolated by GitLab instance and agent. Periodt. 👑

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

These are inherited from parent commands, bestie — not invented here, just passed down like a cute hand-me-down. 🫶

• -h, --help[=false] — show help for this command. 💖
• -R, --repo="" — select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. ✨

🦋 SEE ALSO 🦋

Go peek at these too, iykyk:

• glab-cluster-agent(1)
• glab-cluster-agent-token-cache-clear(1)
• glab-cluster-agent-token-cache-list(1)

---

This page was auto generated by spf13/cobra, dated Nov 2026, and it belongs to the glab(1) manual. Byeee bestie 🫶💖✨