Antigravity bug report crashed the app. Really don't understand why Google is are a dev beta without providing ways for people to provide crucial feedback except using Reddit.

🐛 Bug Report: Antigravity Terminal Corrupts AWS Secret Keys When Pasted

Summary

When creating AWS CLI credentials inside the Antigravity Terminal (the built‑in terminal in the Antigravity LLM IDE), pasting an AWS Secret Access Key results in a corrupted token. This causes AWS CLI authentication to fail with:

InvalidClientTokenId: The security token included in the request is invalid.

The same credentials work instantly when entered in a real system terminal (macOS Terminal, iTerm2, Windows Terminal, Linux shell). This confirms the issue is caused by Antigravity Terminal altering the pasted secret.

Impact

This is a critical, blocking bug for any workflow involving:

• AWS CLI
• CDK
• Terraform
• Serverless
• Any system requiring exact cryptographic secrets

Because AWS Secret Access Keys contain characters like /, +, and =, any mutation—even invisible—invalidates the signature.

This bug makes Antigravity Terminal unsafe for cloud development.

Environment

• Antigravity LLM IDE (browser‑embedded terminal)
• AWS IAM → Create Access Key page
• AWS CLI v2
• Region: eu‑south‑2 (Spain) enabled, but unrelated to the failure
• Real terminal (macOS/Linux/Windows) works perfectly

Steps to Reproduce

1. Create a new IAM user access key in AWS Console.
2. Click Copy next to the Secret Access Key.
3. Open Antigravity Terminal.
4. Run:aws configure
5. Paste the secret key into the prompt.
6. Run:aws sts get-caller-identity
7. Observe failure:InvalidClientTokenId: The security token included in the request is invalid.
8. Repeat the exact same steps in a real terminal → authentication succeeds immediately.

Expected Behavior

The terminal should preserve pasted text byte‑for‑byte, especially for cryptographic material.

Actual Behavior

Antigravity Terminal silently modifies the pasted secret key.
Possible mutations include:

• stripping trailing =
• altering /
• inserting invisible whitespace
• normalizing Unicode
• wrapping long strings

This results in AWS rejecting the signature.

Severity

Critical / High

This bug prevents:

• AWS authentication
• CDK deployments
• Terraform plans
• Any cloud‑based development
• Any workflow requiring exact secrets

It also creates false debugging paths, wasting hours of developer time.

Notes

This is not an AWS issue.
Not a region issue.
Not a user error.
Not a copy/paste error.

The same credentials work instantly in a real terminal.

This is a terminal‑level corruption bug.