What problem does it solve? AI agents inherit the shell's default gh authentication, which is usually 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. ## Core Features & Use Cases - Identity Detection: Check the active GitHub account and token scopes with gh auth status before any operation. - Per-Account Token Extraction: Pull a specific account's token with gh auth token --user without switching the global default, then use it inline for pushes and PR creation. - 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 on a corporate machine needs to push a blog post to a personal GitHub Pages repo. It extracts the personal token at runtime, pushes via token-authenticated HTTPS, and resets the remote URL so no credential persists. ## Quick Start Ask the agent to check the current GitHub identity with gh auth status and push a branch to your personal repository using the correct account token.