New qwen-token-refresh.sh script provides automatic token refresh
for OpenClaw, NanoBot, PicoClaw, NanoClaw (ZeroClaw has native support).
Features:
- Check token status and expiry
- Auto-refresh when < 5 min remaining
- Background daemon mode (5 min intervals)
- Systemd service installation
- Updates both oauth_creds.json and .env file
Usage:
./scripts/qwen-token-refresh.sh --status # Check status
./scripts/qwen-token-refresh.sh # Refresh if needed
./scripts/qwen-token-refresh.sh --daemon # Background daemon
./scripts/qwen-token-refresh.sh --install # Systemd service
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Mark Qwen OAuth as recommended default provider
- Update model reference to coder-model (qwen3-coder-plus)
- Add default provider setup instructions
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Based on ZeroClaw implementation study:
- Change API endpoint from api.qwen.ai to dashscope.aliyuncs.com/compatible-mode/v1
- Update credentials file reference to oauth_creds.json
- Add ZeroClaw native qwen-oauth provider documentation
- Add API endpoints and models reference table
- Update import script with correct endpoint and platform support
- Add PicoClaw and NanoClaw platform configurations
Key findings from ZeroClaw binary:
- Native qwen-oauth provider with auto token refresh
- Uses DashScope OpenAI-compatible endpoint
- Reads ~/.qwen/oauth_creds.json directly
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Document ZeroClaw's native qwen-oauth provider with auto token refresh
- Explain two import methods: Native vs OpenAI-compatible
- Add OAuth credentials structure documentation
- Add comparison table showing feature differences
- Update platform table to show ZeroClaw has Native (not Import) OAuth support
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
·