Vercel KMS signs JWTs from your Functions, no private keys to store
Managed asymmetric keys, a public JWKS endpoint and per-env grants — plus GLM-5.3 hits Vercel's Gateway and Claude Code patches a permission slip.
Copy markdown
Sign tokens without ever touching a private key
Vercel KMS (beta, all plans) lets a Function sign JWTs and arbitrary messages with managed asymmetric keys — RSA, ECDSA or EdDSA. The private key never lives in your code or env vars; the Function authenticates with its OIDC token and asks KMS to sign. That kills the 'secret committed to the repo' class of leak for token issuance.
Verify anywhere with a standard JWKS URL
Public keys publish to https://kms.vercel.com/<issuerId>/jwks.json, so any service verifies your tokens with an off-the-shelf JOSE/OIDC library — no shared secret to hand around. Rotate keys from the CLI or dashboard and previously issued tokens keep validating against the published set.
Lock down what each environment can claim
Grants are per-environment (production, preview, dev, custom), and you can constrain claimable fields with JSON Schema — so a preview deploy can't mint a token that says admin:true. It's the fine-grained service-to-service auth you'd normally stand up a cloud KMS for, without the KMS bill.
Elsewhere: GLM-5.3 lands on Vercel's AI Gateway
Z.ai's GLM-5.3 coding model — which shipped plan-only last week — is now callable through Vercel's AI Gateway at list price with no markup or platform fee, plus automatic fallbacks and per-request traces. If you wanted GLM-5.3 inside your own app instead of a chat plan, this is the API door.
Elsewhere: Claude Code 2.1.235 closes a permission slip
The Aug 18 build fixes a bug where Shift+Tab in a permission prompt could approve edits you didn't mean to, plus whole-prompt-cache invalidation when language servers reconnect; it also adds an opt-in spellcheck setting. Worth updating if you're on 2.1.234 or earlier.