Qwen Portal Auth Helper

Battle-tested solution for qwen-portal OAuth automation
Solves the "interactive TTY required" problem, prevents cron task failures, and provides full monitoring.

🚨 The Problem

qwen-portal provides free models (2,000 requests/day) but OAuth expires every 1-2 weeks. When it expires:

1. 1. Cron tasks fail with: INLINECODE0
2. INLINECODE1 fails: INLINECODE2
3. Manual intervention required, breaking automation
4. Tasks remain in error state even after authentication fix

💡 The Solution

This skill provides a complete solution:

• - Automated OAuth link extraction using tmux (bypasses TTY requirement)
• Health monitoring for qwen-portal tasks
• Self-healing scripts to fix task states
• Documented best practices from real-world experience

📦 Installation

CODEBLOCK0

🛠️ Quick Start

Get OAuth Link (when authentication expired)

~/.openclaw/skills/qwen-portal-auth-helper/scripts/get-qwen-oauth-link.sh

Outputs: CODEBLOCK2

Check Authentication Health

~/.openclaw/skills/qwen-portal-auth-helper/scripts/check-qwen-auth.sh

Checks all qwen-portal tasks, reports errors, generates actionable report.

Setup Weekly Monitoring

CODEBLOCK4

🔧 Core Features

1. OAuth Link Automation

CODEBLOCK5

How it works: Uses tmux to create virtual terminal, captures output before command hangs.

2. Health Monitoring

• - Scans all cron tasks using qwen-portal models
• Detects error states and consecutive failures
• Generates detailed reports with actionable advice
• Early warning before complete failure

3. Recovery Tools

• - Resets task error states after authentication fix
• Provides step-by-step recovery checklist
• Validates fixes actually work

4. Best Practices Documentation

• - Complete workflow from diagnosis to recovery
• Common pitfalls and how to avoid them
• Maintenance schedule recommendations

📋 Complete Workflow

When tasks start failing:

CODEBLOCK6

Weekly Maintenance:

CODEBLOCK7

🎯 Use Cases

1. AI Assistants & Automation

AI assistants can't provide interactive TTY. This skill enables them to:

• - Automatically detect qwen-portal auth issues
• Get OAuth links for user approval
• Complete the recovery process

2. Cron Task Reliability

Ensure scheduled tasks don't fail due to expired OAuth:

• - Weekly health checks
• Early detection of impending expiry
• Automated recovery procedures

3. Team Collaboration

Standardized approach for teams:

• - Everyone uses same proven method
• Documentation prevents repeated mistakes
• Shared monitoring and alerting

4. New User Onboarding

New OpenClaw users inevitably hit this issue. This skill provides:

• - Immediate solution without trial-and-error
• Complete documentation
• Community-validated approach

🔍 Technical Details

How OAuth Link Extraction Works

CODEBLOCK8

Key discoveries from real-world testing:

• - Link format is always: INLINECODE3
• Device code: 7 uppercase alphanumeric characters (e.g., M17WU0SC)
• Command hangs after showing link (◑ Waiting for Qwen OAuth approval...)
• Must capture output actively, not wait for completion

Task State Management

Even after successful authentication, cron tasks may remain in error state: CODEBLOCK9

This skill includes scripts to reset these states automatically.

📊 Monitoring & Alerting

What We Monitor

1. 1. Task Status: Error vs OK
2. Consecutive Errors: >3 triggers warning
3. Last Success Time: Tasks not running recently
4. OAuth Expiry Estimate: Based on 1-2 week pattern

Alert Thresholds

• - Warning: 3+ consecutive errors
• Critical: Task in error state + OAuth-related error message
• Recovery Needed: Manual intervention required

Reports Generated

• - Weekly health report
• Error analysis with suggested fixes
• Maintenance checklist
• Historical trends

🚀 Advanced Usage

Integration with Other Skills

CODEBLOCK10

Custom Monitoring Schedule

CODEBLOCK11

Extending for Other OAuth Providers

The pattern works for other services with similar issues:

1. 1. GitHub OAuth
2. Google OAuth
3. Other AI model providers with device-code flow

📝 Examples

Example 1: Quick Recovery

CODEBLOCK12

Example 2: Proactive Maintenance

CODEBLOCK13

Example 3: Integration with AI Assistant

CODEBLOCK14

⚠️ Common Pitfalls & Solutions

Pitfall 1: Command hangs indefinitely

Solution: Use timeout and active output capture (implemented in scripts)

Pitfall 2: ANSI escape codes break parsing

Solution: Robust regex that handles colored output (included)

Pitfall 3: Task state doesn't reset automatically

Solution: Manual state reset scripts (provided)

Pitfall 4: Multiple qwen-portal tasks failing

Solution: Batch processing in monitoring script

Pitfall 5: OAuth expires at inconvenient times

Solution: Weekly monitoring catches it early

🔄 Maintenance Schedule

Weekly (Essential)

• - Run health check script
• Review error reports
• Prepare for potential re-authentication

Monthly (Recommended)

• - Review OAuth expiry patterns
• Update scripts if qwen-portal changes
• Clean up old log files

Quarterly (Optional)

• - Test complete recovery workflow
• Update documentation
• Check for new best practices

🤝 Community & Support

Based on Real Experience

This skill was developed from solving actual production issues on 2026-03-09:

• - Two critical news collection tasks failing
• 9-10 consecutive errors before detection
• Multiple failed attempts before finding tmux solution
• Documented in .learnings/ system

Contributing

Found a better way? Have another OAuth provider with similar issues?

1. 1. Fork the repository
2. Add your improvements
3. Submit pull request
4. Help others avoid the same pitfalls

Getting Help

• - Check examples/ directory for common scenarios
• Review docs/troubleshooting.md for known issues
• Open issue on repository for new problems

📈 Benefits

For Individual Users

• - No more manual OAuth link hunting
• Prevent task failures before they happen
• Standardized recovery process
• Less time spent on maintenance

For Teams

• - Shared knowledge and tools
• Consistent monitoring approach
• Reduced support requests
• Faster onboarding for new members

For Community

• - Open source solution to common problem
• Continuously improved by users
• Foundation for other OAuth automation
• Knowledge sharing prevents repeated mistakes

🎉 Getting Started

Installation

CODEBLOCK15

First-Time Setup

CODEBLOCK16

Verify It Works

# Simulate a failure scenario
openclaw cron run <your-qwen-portal-task-id>

# Check monitoring catches it
./scripts/check-qwen-auth.sh

# Practice recovery workflow
./scripts/get-qwen-oauth-link.sh --dry-run

---

Remember: qwen-portal OAuth expires every 1-2 weeks. Solution: Weekly monitoring + this skill = no more surprises.

Skill version: 1.0.0 | Based on 2026-03-09 battle-tested experience