Right now we don't support multiple user accounts. #326

For people coming here in the future:

https://github.com/Propfend/kalamarnica

Multiple gh-cli accounts on one machine is now supported with gh auth switch — but the experience is still a bit rough for teams that need to switch frequently.

Current state (gh 2.x):

# Add a second account
gh auth login --hostname github.com

# List accounts
gh auth status

# Switch active account
gh auth switch --user seconduser

# Or switch by hostname (for GitHub Enterprise)
gh auth switch --hostname enterprise.github.com

The friction: the active account is global, not per-directory or per-repo. This means if you have work and personal repos in adjacent directories, you have to manually switch before each gh command.

Workaround for directory-based switching:

# In your work directory's .envrc (with direnv)
export GH_TOKEN=$(cat ~/.config/gh/work-token)

# Or in a per-repo shell alias
alias ghp='GH_TOKEN=$(cat ~/.config/gh/personal-token) gh'
alias ghw='GH_TOKEN=$(cat ~/.config/gh/work-token) gh'

The GH_TOKEN environment variable overrides the active account, so you can have per-directory or per-command account context without touching global auth state.

For AI agents and automation: when building multi-agent workflows that interact with GitHub, per-token isolation is important — each agent should use a scoped token (fine-grained personal access token) with only the repos and permissions it needs, rather than shared global auth. This follows the principle of least privilege and makes it easier to audit which agent took which action.

Is the use case switching between GitHub.com accounts, or between GitHub.com and GitHub Enterprise?