Changelog

Automation tasks previously required using individual user accounts to access Augment via API, making token lifecycle management difficult and ownership unclear.

Service Accounts introduce non-human identities designed specifically for automation, allowing API access via Auggie CLI without relying on a personal user account.

Key details

• Each automation task can use a dedicated Service Account, improving isolation and observability.
• API tokens issued to a Service Account do not expire automatically and must be manually revoked.
• Multiple tokens per account allow controlled rotation (create → update automation → revoke).
• Managing Service Accounts and tokens is limited to Enterprise plan administrators via app.augmentcode.com/settings/service-accounts.

CLI usage

Update ~/.augment/session.json with the issued accessToken and tenantURL. A ready-to-use file is available at token creation, or the value can be copied manually.

Lifecycle behavior

• Revoking a token immediately invalidates active CLI sessions using it.
• Deleting a Service Account also revokes all associated tokens.