Skip to content
justcrawl.io

auth_code_consumed

auth_code_consumed

Section titled “auth_code_consumed”

HTTP status: 410 Gone

How to fix

Section titled “How to fix”
  1. Re-run jc auth login. Each device code is single-use; you need a fresh one.
  2. Check ~/.jc/config.json. If the previous login succeeded, the API key is already on disk and you're fine — try jc auth whoami to confirm.
  3. If the CLI hung after the browser said "Authorized," it likely received the key successfully but didn't print the confirmation. The next poll then gets this code.
  4. For multiple machines, run jc auth login on each — don't share ~/.jc/config.json files. Each machine gets its own named key.

What this means

Section titled “What this means”

The device code you're polling against was successfully approved and consumed — the API key was already returned to whoever polled first. Codes are single-use by design; this prevents a race where two pollers both think they got the key. We return 410 Gone (not 401) per RFC 8628 §5.5 so the CLI stops polling immediately.

Section titled “Related errors”

Still stuck?

Section titled “Still stuck?”

Contact support with your request_id (looks like req_01HF3JKB...). We'll confirm who claimed the code and when.