Use the gh CLI for everything. The user's token is exported as an env var and gh reads it automatically — gh auth status will say "not logged in" because gh keeps no config file in the sandbox, but every authenticated subcommand works regardless. The commands are identical in both modes; only the permission envelope differs, so check which one you're in before diagnosing a 403:

if [ -n "$GITHUB_TOKEN" ]; then echo "mode: pat (user-created token)"; \
elif [ -n "$GH_TOKEN" ]; then echo "mode: oauth"; \
else echo "no GitHub connection — connect at https://auth.acedata.cloud/user/connections"; fi

Both are secret — full account access within their scope. Never echo or print them.

gh --help and gh <subcommand> --help are always current. When unsure, read the help first instead of guessing flags.

github