From 46d15e30ea0475798cb01c99569b0da79af103e2 Mon Sep 17 00:00:00 2001 From: Justin Xu Date: Sun, 7 Sep 2025 20:13:55 -0700 Subject: [PATCH 1/2] Minor readme update Update README.md with non-deprecated syntax --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8bf9513..7073c0f 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ Example session JSON: There are 2 ways to get the credentials: -- Run `auggie --print-augment-token` +- Run `auggie tokens print` - Copy the JSON after `TOKEN=` - Copy the credentials stored in your Augment cache directory, defaulting to `~/.augment/session.json` From 2b5b11644fd86ec2dc7f8b809b303460f5f42969 Mon Sep 17 00:00:00 2001 From: Justin Xu Date: Wed, 10 Sep 2025 10:41:48 -0700 Subject: [PATCH 2/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7073c0f..beb31d8 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ There are 2 ways to get the credentials: > - Never commit them to version control > - Only store them in secure locations (like GitHub secrets) > - Don't share them in plain text or expose them in logs -> - If a token is compromised, immediately revoke it using `auggie --revoke-all-augment-tokens` +> - If a token is compromised, immediately revoke it using `auggie tokens revoke` ### 2. Set Up the GitHub Repository Secret