Summary
Getting You are not logged in to GitHub CLI errors with gh aw add-wizard command even after logging in to gh CLI.
While the gh aw add works as expected in the same scenario.
Same behavior observed in:
- Windows Terminal PowerShell 7.
- A dev container running on the same Windows machine with WSL.
- A different Windows computer and different GitHub account.
Reproduction
Setup:
- In Windows using Windows Terminal PowerShell 7.
- gh version 2.89.0 (2026-03-26)
- gh aw version v0.67.1
First login to gh CLI using:
gh auth login --hostname github.com --git-protocol https --web
Run:
gh aw add-wizard githubnext/agentics/daily-repo-status -verbose
Error
Full output of the command:
ℹ Auto-detected GitHub Enterprise host: bryanknox@github.com
🚀 Welcome to GitHub Agentic Workflows!
This tool will walk you through adding an automated workflow to your repository.
ℹ Fetching githubnext/agentics/workflows/daily-repo-status.md@main...
ℹ Resolved to commit: 7c7feb6
✓ Downloaded workflow (1558 bytes)
ℹ This workflow creates daily repo status reports. It gathers recent repository
activity (issues, PRs, discussions, releases, code changes) and generates
engaging GitHub issues with productivity insights, community highlights,
and project recommendations.
✗ You are not logged in to GitHub CLI.
Please run the following command to authenticate:
⚡ gh auth login
✗ not authenticated with GitHub CLI
Workaround
Use gh aw add instead of gh aw add-wizard.
Summary
Getting
You are not logged in to GitHub CLIerrors withgh aw add-wizardcommand even after logging in to gh CLI.While the
gh aw addworks as expected in the same scenario.Same behavior observed in:
Reproduction
Setup:
First login to gh CLI using:
Run:
Error
Full output of the command:
Workaround
Use
gh aw addinstead ofgh aw add-wizard.