Amp July 14, 2026 Changelog
What changed in Amp coding agent July 14, 2026, released 2026-07-14 — explained in plain English.
- Amp environments (called "orbs") can now prove who they are to outside services.
- You no longer need to paste permanent passwords (secrets) into your settings to give orbs access.
- Temporary ID tokens let orbs safely read logs, decrypt files, or share local demos.
- Every action is trackable back to the exact user and project, making it highly secure.
Want a heads-up when Amp updates?
We email you the moment a new Amp version drops — plus plain-English release notes like these. No spam.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
This update is all about making it safer for developers to connect their Amp environments to outside tools and cloud services. It matters most to anyone who manages infrastructure or needs to securely access production systems, because it replaces risky, hardcoded passwords with temporary, highly trackable digital ID badges.
What's new
- Digital ID Badges for Orbs: Your orbs can now use a system called OIDC (OpenID Connect) to prove their identity to other services. Instead of sharing a permanent password, the orb gets a temporary "token" (a digital ID card) that outside services can check to see exactly who is asking for access.
- Custom Tracking Details: When an orb generates one of these ID tokens, it includes standard info like the expiration time, but it also adds custom details. This means the token tells the outside service exactly which workspace, project, and user is asking for access, and even which specific conversation thread it came from.
Improvements
- Zero-Setup Access: You can now connect outside services (like Google Cloud) to trust Amp orbs automatically. For example, you can give every orb in your workspace read-only access to production logs without developers needing to configure anything themselves.
- Safer Secret Management: Instead of managing dozens of secret passwords in your project settings, you can lock up encrypted files in your code repository. Your orb can use its new digital ID to ask a service like AWS to unlock those files only when it needs them.
- Better Local Sharing: You can use these ID tokens to securely connect to networks like Tailscale. This lets you share local demo apps running in your orb with coworkers, without exposing them to the whole internet.
- Temporary Permissions: You can set up scripts that let your orb ask for "escalated privileges" (temporary admin powers) for a specific task, making sure higher-level access is only granted exactly when needed.
Fixes
No fixes were mentioned in this release.
Breaking changes
No breaking changes in this release.
How to upgrade
Update to Amp July 14, 2026 by running:
npm install -g @ampcode/cliThis is our plain-language summary. Read the complete, official notes on the Amp official changelog ↗.
Google Calendar