What problem does it solve? AI agents and developers working with both an Enterprise Managed User (EMU) GitHub account and a personal account often hit permission errors when pushing to personal repos or creating PRs on forks, because the shell's default gh authentication is the wrong identity. ## 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 to maintain fully separate gh configurations for EMU and personal accounts, with shell aliases for quick switching. - Use Case: An agent whose shell defaults to an EMU account needs to push a blog post to a personal GitHub Pages repo; it extracts the personal token, pushes via token-authenticated HTTPS, then cleans the remote URL so no token persists. ## Quick Start Ask the agent to check which GitHub account is active and push the current branch to your personal repository using the correct identity.
