aisw
aisw stands for AI Switcher. It is a multi-account manager and account switcher for Claude Code, Codex CLI, and Gemini CLI, built to help you switch AI CLI accounts without manually copying credential files, editing config directories, or re-running login flows every time you hit a usage limit.
Install
Section titled “Install”Shell installer
Section titled “Shell installer”curl -fsSL https://raw.githubusercontent.com/burakdede/aisw/main/install.sh | shcargo install aiswWatch aisw work
Section titled “Watch aisw work”What aisw helps with
Section titled “What aisw helps with”Developers usually find aisw when they are trying to solve one of these problems:
- switch between multiple Claude Code accounts
- switch between multiple Codex CLI accounts
- switch between multiple Gemini CLI accounts
- manage several AI CLI subscriptions on one machine
- rotate between work and personal AI coding tool profiles
- keep Claude, Codex, and Gemini credentials organized without manual file copying
If you were searching for an AI CLI account switcher, a multi-account CLI manager, or a way to manage multiple Claude, Codex, or Gemini logins locally, this documentation is the right place to start.
Start here
Section titled “Start here”| Document | Description |
|---|---|
| Why aisw? | Why you need an AI agent account manager |
| Quickstart | Install aisw, run first-time setup, and switch accounts quickly |
| Commands | Full reference for all subcommands and flags |
| Adding Profiles | OAuth and API key auth flows per tool |
| Automation and Scripting | Prompt behavior, JSON output, stdout/stderr expectations, and scripting patterns |
Value at a glance
Section titled “Value at a glance”- Zero Manual File Copying: Switch profiles with one command. No more searching for hidden
.envor.credentials.jsonfiles. - Safety First: Automatic backups before every switch and enforced
0600permissions. - Identity Awareness: Prevent duplicate aliases by automatically resolving account emails and IDs.
- Seamless Setup:
aisw initimports your existing credentials in seconds.
Setup and operation
Section titled “Setup and operation”| Document | Description |
|---|---|
| Shell Integration | Shell hook setup for bash, zsh, fish |
| Supported Tools | Tool compatibility, binary names, auth methods |
| Configuration | ~/.aisw/config.json schema and settings |
Common questions
Section titled “Common questions”- Troubleshooting: Issues with shell hooks, tool detection, or permissions.
- What aisw actually changes when I switch accounts?
- Does aisw send credentials or prompts over the network?
- Where are profiles stored, and how are they protected?
What does aisw actually change when I switch accounts?
Section titled “What does aisw actually change when I switch accounts?”aisw use applies the selected profile into the live config location that Claude Code, Codex CLI, or Gemini CLI already reads. It does not patch the tool binary, install a proxy, or change anything outside the relevant local credential and config files.
Does aisw send credentials or prompts over the network?
Section titled “Does aisw send credentials or prompts over the network?”No. aisw itself does not proxy requests, inspect prompts, or send your credentials to a remote service. It is a local credential and profile switcher.
Where are profiles stored, and how are they protected?
Section titled “Where are profiles stored, and how are they protected?”Stored profiles live under ~/.aisw/profiles/<tool>/<name>/. Credential files are written with 0600 permissions so only your user can read or write them, and aisw status reports files that are broader than that.
Can I use this for work, personal, and backup accounts across different tools?
Section titled “Can I use this for work, personal, and backup accounts across different tools?”Yes. A common setup is separate work, personal, client, or backup profiles for Claude Code, Codex CLI, and Gemini CLI so you can switch in seconds when a quota runs out or you need a different subscription.