GitHub authentication problems prevent Helmor from listing remote repositories, resolving your account identity, or performing pull request actions. Here is how to diagnose and fix them.

Symptoms#

• Helmor cannot list your GitHub repositories.
• The app shows a "Connect GitHub" prompt for a repo you already authorized.
• Pull request or push actions fail with permission errors.
• Your account name or avatar does not appear in Settings.

Diagnosis steps#

1. Confirm account access — open github.com in a browser and verify you can see the repository in question.
2. Check token status — go to Settings → GitHub in Helmor. If the connection shows as expired or disconnected, proceed to re-authentication.
3. Review org permissions — if the repo belongs to an organization with SSO, ensure your Helmor OAuth app is authorized under the org's third-party access settings.

Fix: re-authenticate#

1. Open Settings → GitHub in Helmor.
2. Click Disconnect, then Sign in with GitHub again.
3. Re-authorize the repositories or organizations you need.
4. Retry the failing action (import, push, or PR creation).

Fix: organization SSO#

If your org enforces SAML SSO:

1. Go to github.com → Settings → Applications → Authorized OAuth Apps.
2. Find Helmor and click Grant next to your organization.
3. Reconnect in Helmor's settings.

Local fallback#

If GitHub remains unavailable, you can still:

• Use local repositories with full agent workflow support.
• Commit changes locally and push manually via terminal.

Remote branch context and PR features will be limited until authentication is restored.

When to escalate#

If re-authentication does not resolve the issue, capture the exact action, repository name, account, and error text, then file an issue at github.com/dohooo/helmor/issues.