-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Description
clawhub.ai redirects to www.clawhub.ai (HTTP 307), but the CLI doesn't follow this redirect for authentication requests, causing "Unauthorized" errors.
Steps to Reproduce
npx molthub@latest login --token "valid_token" --no-browser
# Result: Unauthorized
npx molthub@latest login --token "valid_token" --no-browser --registry "https://www.clawhub.ai"
# Result: SuccessRoot Cause
curl -I https://clawhub.ai/api/v1/me
# HTTP/2 307 → Location: https://www.clawhub.ai/api/v1/meThe CLI doesn't follow this redirect for auth verification.
Impact
Users get confusing "Unauthorized" errors with valid tokens. Must manually specify --registry flag.
Suggested Fix
Either:
- Follow redirects for all requests including auth
- Default to
www.clawhub.ai - Provide clearer error: "Registry redirected to X, retry with --registry X"
Found during seller flow UX testing
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working