CLI Tools
Qwen Code
Select OpenAI authentication and set the endpoint and model.
The vendor documents custom endpoints. Check model capabilities and verify the connection.
On this page
Before you begin
Install current Qwen Code and its required Node.js version. This setup uses an API key rather than the Qwen OAuth allowance.
Have an A2Agent API key ready and copy an accessible model ID from the catalog. Replace every placeholder, back up existing settings and keep keys out of repositories.
Setup
File contents are usually shared; switching OS changes commands and paths. For WSL on Windows, select macOS / Linux.
01Install Qwen Code
Run qwen --version after installation and check that an older executable is not taking precedence.
Open official documentationShellnpm install -g @qwen-code/qwen-code@latest qwen --version02Select OpenAI authentication
Replace the model ID and key, then run in the same terminal.
Shellexport OPENAI_BASE_URL='https://a2agent.me/v1' export OPENAI_API_KEY='YOUR_A2AGENT_API_KEY' export OPENAI_MODEL='YOUR_MODEL_ID' qwen --auth-type openai --model YOUR_MODEL_ID
Capabilities and limits
- Legacy auth.apiKey and auth.baseUrl settings are deprecated. Prefer provider configuration or environment variables after updating.
- A successful OAuth login does not verify A2Agent routing. Check for usage in the A2Agent console.
Verify the connection
Replace every placeholder and run locally. Expect JSON containing OK. Then start a new client conversation, test one read-only tool call separately, and confirm the requests in A2Agent usage records. This test incurs a small amount of model usage.
curl --fail-with-body --silent --show-error --max-time 60 'https://a2agent.me/v1/chat/completions' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer YOUR_A2AGENT_API_KEY' \
-d '{"model":"YOUR_MODEL_ID","max_tokens":128,"messages":[{"role":"user","content":"Reply with OK."}]}'Troubleshooting
If Qwen OAuth is still used, check --auth-type openai and any authentication override in project settings.json.
401 / 403: authentication or access denied
Use a key issued by A2Agent, without extra spaces, and check that it is active and unexpired. Confirm the group permits the model and protocol. A vendor subscription credential cannot replace an A2Agent key.
404 / model not found: endpoint or model mismatch
Check the root URL, /v1 prefix and full request path against this guide; avoid duplicated paths. Model IDs are case-sensitive and must be accessible to the current key.
429: quota or rate limit
Check your balance, key limits, concurrent usage and service status. Wait before retrying and reduce simultaneous agents; repeated retries do not remove a quota limit.
Chat works, but tools fail or streaming stops
Test a short text request, then a single read-file tool call. Check tool support, output budget, proxy timeouts and client version. Inspect the diff before resuming a long task to avoid repeating actions.
Restore previous settings
Close the terminal and restore the previous authentication choice. Remove these three variables if saved in .env or a shell profile.
Sources and check date
Status is based on official configuration docs, not end-to-end client testing with A2Agent.
Docs checked 2026-09-18
