#ClawHub login stuck after account deletion — GitHub ID residual data?

1 messages · Page 1 of 1 (latest)

toxic inlet
#

Hi, I previously linked my GitHub account to ClawHub (GitHub ID: 208269246), then deleted my ClawHub account. Now when I try to sign in again with the same GitHub, it gets stuck on the CLI login page — nothing happens after clicking "Sign in with GitHub". I've already revoked the OAuth app in GitHub settings and cleared browser cookies. Could you check if there's residual data tied to this GitHub ID blocking re-registration? Thanks! @paper valley

prime ingotBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

paper valleyBOT
#

I can’t directly inspect ClawHub’s backend/user records from Discord (so I can’t confirm “residual data” for GitHub ID 208269246 from here), but this usually ends up being a CLI loopback login flow issue rather than a “GitHub ID is permanently blocked” thing.

ClawHub CLI login works like: it starts a local server on 127.0.0.1:<randomPort>, opens https://clawhub.ai/cli/auth?...redirect_uri=http://127.0.0.1:<port>/callback..., then the browser should bounce back to your localhost callback.

Quick things to try (most common fixes)

  1. Try a different browser / clean profile
  • Chrome/Edge incognito, with extensions disabled (adblock/privacy tools often break the “Sign in with GitHub” button).
  • Make sure popups/redirects aren’t blocked for clawhub.ai.
  1. See if the redirect-to-localhost is what’s failing
  • After GitHub auth, you should land on something like:
    http://127.0.0.1:XXXXX/callback?...
  • If you get a “can’t connect” / blank / stuck page there, it’s typically VPN/proxy/firewall blocking localhost callbacks, or the CLI isn’t actually listening anymore.
  1. Bypass the whole browser-loopback flow (recommended workaround)
  • Sign into the website directly: https://clawhub.ai
  • Go to Settings → API tokens, create a token
#
  • Then log in headlessly via CLI:
    clawhub login --token clh_...
    (Don’t paste the token into Discord—treat it like a password.)
  1. Reset local CLI config (in case it’s stuck in a bad state)
  • Per ClawHub docs, macOS default config is:
    ~/Library/Application Support/clawhub/config.json
  • If you tell me your OS, I can point you at the right config location / env var override to try (CLAWHUB_CONFIG_PATH).

If you want this investigated as a bug

Please open an issue here (that’s the right place for someone with access to check server-side state):
https://github.com/openclaw/clawhub/issues

Include:

  • OS + clawhub --version