Why aisw?
If you use AI coding agents like Claude Code, Codex CLI, or Gemini CLI, you eventually hit a usage limit. Whether it’s a daily quota, a monthly token cap, or a rate limit, the result is the same: your workflow stops.
aisw was built to ensure your momentum isn’t broken by subscription boundaries.
The Problem: Friction and Risk
Section titled “The Problem: Friction and Risk”Before aisw, switching accounts was a manual, error-prone process:
- Manual File Management: You had to find and move hidden files like
~/.claude/.credentials.jsonor edit~/.gemini/.envmanually. - Identity Confusion: It was easy to lose track of which account was currently “live,” leading to accidental usage of the wrong subscription.
- Security Risks: Manually copying sensitive credentials increases the risk of setting loose permissions or accidentally leaking them in a terminal history or git repo.
- No Backups: If you messed up a manual copy, your login session was gone, forcing you to re-run the browser OAuth flow.
The Solution: Seamless, Secure Switching
Section titled “The Solution: Seamless, Secure Switching”aisw transforms account management into a single-command operation.
1. Atomic Switching
Section titled “1. Atomic Switching”When you run aisw use, the change is atomic. We handle the file moves, permission settings, and environment variables in one shot. You don’t have to remember where the tools store their secrets; aisw already knows.
2. Built-in Security
Section titled “2. Built-in Security”We treat your credentials as a “vault.” All profiles are stored with 0600 (owner read/write only) permissions. aisw status acts as a security auditor, warning you if any live credential files have overly permissive access.
3. Identity Awareness
Section titled “3. Identity Awareness”aisw isn’t just a file copier; it’s identity-aware. When you add or import a profile, it inspects the credentials to resolve a unique identity (like an email or account ID). This prevents you from creating duplicate aliases for the same account, keeping your profile list clean.
4. Safety Net (Automatic Backups)
Section titled “4. Safety Net (Automatic Backups)”Every time you switch profiles, aisw takes a snapshot of the current state. If a switch goes wrong or a tool’s config format changes, you can restore your credentials with aisw backup restore.
Comparison: Manual vs. aisw
Section titled “Comparison: Manual vs. aisw”| Feature | Manual Switching | Using aisw |
|---|---|---|
| Speed | 1-2 minutes (finding files, renaming) | < 2 seconds |
| Reliability | High risk of file corruption/loss | Atomic, verified operations |
| Security | Manual permission management | Automatic 0600 enforcement |
| Organization | Messy .old or .backup files | Named profiles with labels |
| History | None | Automatic switch snapshots |
Who is it for?
Section titled “Who is it for?”- Power Users: Developers who maintain multiple subscriptions to bypass daily quotas.
- Freelancers: Engineers who need to switch between client-provided accounts and personal ones.
- Teams: Developers who share a “team” account but keep personal experiments on a separate profile.
- Security-Conscious Users: Anyone who wants a centralized, audited location for their AI agent credentials.
Ready to get started? Head over to the Quickstart.