What problem does it solve? AI agents inherit the shell's default gh authentication, which is often an Enterprise Managed User (EMU) account. This causes failures when agents push to personal repos, create PRs on forks, or access resources outside the enterprise org, and naive fixes like global auth switching break parallel agents. ## Core Features & Use Cases - Identity Detection: Check the active GitHub account and token scopes with gh auth status before any operation. - Per-Operation Token Extraction: Pull a specific account's token with gh auth token --user and use it inline for pushes or PR creation without switching the global default. - Config Directory Isolation: Use GH_CONFIG_DIR and shell aliases to fully separate EMU and personal account contexts. - Use Case: An agent on an EMU-authenticated shell needs to push a blog post to a personal GitHub Pages repo. It extracts the personal token, pushes via token-authenticated HTTPS, then resets the remote URL so no credential persists. ## Quick Start Ask the agent to check gh auth status and push the current branch to your personal GitHub repo using your personal account token.