Authentication Issues
Not logged in error
Not logged in error
Error:
Not logged in. Please run "anyware login" first.Solution: Run anyware login to authenticate. If you’ve already logged in, your credentials may have expired.Login fails or times out
Login fails or times out
Error: Authentication fails or browser doesn’t respondSolutions:
- Make sure your browser opens the verification URL
- Check that you’re confirming the correct device code
- If the code expired, run
anyware loginagain
Browser doesn't open automatically
Browser doesn't open automatically
Symptom: Login command doesn’t open browserSolution: Copy the verification URL shown in the terminal and open it manually in your browser. Complete the authentication flow there.
Connection Issues
WebSocket connection failed
WebSocket connection failed
Error: Unable to connect to serverCauses:
- Network firewall blocking WebSocket
- Proxy server interfering
- Server temporarily unavailable
- Check your internet connection
- Try from a different network
- Wait a few minutes and try again
Connection drops
Connection drops
Symptom: Session disconnects unexpectedlyCauses:
- Network instability
- Server maintenance
- The CLI will try to reconnect automatically
- If it doesn’t recover, restart with
anyware - Check your network connection
Session not appearing in dashboard
Session not appearing in dashboard
Symptom: Started a session but dashboard shows nothingSolutions:
- Refresh the dashboard
- Verify you’re logged into the same account
- Check that
anywarestarted without errors
Mode Switching Issues
Remote mode not activating
Remote mode not activating
Symptom: Sent prompt from web but CLI stays in local modeCauses:
- WebSocket connection issue
- Message not received
- Check that the session shows as connected in dashboard
- Try sending the prompt again
- Restart the session if needed
Can't switch back to local mode
Can't switch back to local mode
Symptom: Pressing Enter/Esc doesn’t return controlSolutions:
- Wait for Claude to finish responding
- Press Enter firmly (not other keys)
- If stuck, Ctrl+C to exit and restart
Input going to wrong mode
Input going to wrong mode
Symptom: Typing locally but input goes to web, or vice versaSolution: Check the status bar indicator:
[LOCAL]means terminal input is active[REMOTE]means web input is active
Model Issues
Model not found
Model not found
Error: Invalid model or model not availableSolutions:
- Check the model format:
provider/model-name - Verify the model is available on OpenRouter
- Try a known model like
anthropic/claude-sonnet-4
Model behaving unexpectedly
Model behaving unexpectedly
Symptom: Model giving poor responses or errorsCauses:
- Model has different capabilities than Claude
- Model doesn’t support all Claude Code features
- Try a different model
- Use Claude for complex coding tasks
- Check model documentation for limitations
Claude Code Issues
Claude Code won't start
Claude Code won't start
Error: Failed to spawn Claude CodeCauses:
- Claude Code not installed
- Permission issues
- Verify Claude Code is installed:
claude --version - Check you have execute permissions
- Reinstall Claude Code if needed
Claude shows authentication prompt
Claude shows authentication prompt
Symptom: Claude asks you to log in or provide API keyExpected behavior: Anyware should handle authentication automaticallySolution: This shouldn’t happen. If it does, check that you’re running Claude Code through
anyware, not directly.Dashboard Issues
Dashboard not loading
Dashboard not loading
Symptom: anyware.run won’t load or shows errorsSolutions:
- Try a different browser
- Clear browser cache
- Check your internet connection
- Wait a few minutes (may be temporary outage)
Can't send prompts from dashboard
Can't send prompts from dashboard
Symptom: Input field doesn’t work or messages not sentSolutions:
- Check that the session is active (not ended)
- Refresh the page
- Try a different browser
Output not streaming
Output not streaming
Symptom: Dashboard connected but no output appearingCauses:
- WebSocket connection issue
- Session may have ended
- Refresh the dashboard
- Check if the CLI is still running
- Check your network connection
Billing Issues
Quota exceeded
Quota exceeded
Error: Usage limit reachedSolutions:
- Upgrade your plan when prompted
- Wait for quota to reset at the start of your billing period
- Check usage in the dashboard
Payment issues
Payment issues
Symptom: Checkout fails or payment not processedSolutions:
- Try a different payment method
- Disable browser extensions that might block Stripe
- Contact support if the issue persists
Getting Help
If you can’t resolve your issue:- Check the FAQ for common questions
- Contact support
- CLI version (
anyware version) - OS and architecture
- Full error message
- Steps to reproduce