For the complete documentation index, see llms.txt. This page is also available as Markdown.

Troubleshooting

Common issues and solutions when using TensorX with AI coding tools.


API Error: Cannot read properties of undefined

Cause

Usually happens when environment variables are conflicting or the base URL is incorrect.

Solution

  1. Verify your API base URL:

    • For Claude Code: https://api.tensorx.ai

    • For Cursor/Cline: https://api.tensorx.ai/v1

  2. Replace the placeholder YOUR_API_KEY with your actual TensorX API key

  3. Clear conflicting environment variables:

# For Claude Code
unset ANTHROPIC_AUTH_TOKEN ANTHROPIC_BASE_URL

# For Cursor/Cline
unset OPENAI_API_KEY OPENAI_BASE_URL
  1. Check your API credits at app.tensorx.ai/dashboard


Claude Code: Model Errors or Background Task Failures

Cause

Claude Code requires all 5 model environment variables to be set, even if you only use one model. Missing variables cause background task failures.

Solution

Set all required model variables:


Connection Timeout

Cause

The default timeout may be too short for complex operations.

Solution

Increase the timeout value in your configuration:


Model Not Found

Cause

Using incorrect model ID format.

Solution

Always use the full model ID with provider prefix:

✅ Correct
❌ Incorrect

z-ai/glm-5.1

glm-5.1

minimax/minimax-m2

minimax-m2

minimax/minimax-m2.5

m2.5

Browse all available models at tensorx.ai/models.


Authentication Failed

Cause

Invalid or expired API key.

Solution

  1. Log in to app.tensorx.ai

  2. Navigate to your dashboard

  3. Generate a new API key

  4. Update your configuration with the new key


OAuth Conflict (Claude Code)

Cause

Claude Code's built-in OAuth login conflicts with TensorX configuration.

Solution

If you accidentally trigger OAuth:

  1. Press Ctrl+C to cancel the OAuth prompt

  2. Verify your environment variables are set correctly

  3. Restart Claude Code

Print mode (-p) works without any Anthropic account or OAuth - it's the fastest way to test your setup.


Rate Limiting

Cause

Too many requests in a short period, or too many tokens reserved in a single request.

Diagnosing RPM vs TPM Limits

Check the Limit type field in the 429 error message to determine which limit you hit:

Error message
You hit
Meaning

Limit type: requests

RPM

Too many API calls per minute

Limit type: tokens

TPM

Too many tokens reserved per minute

Solution

  • If you hit RPM: Wait a few seconds between requests, or batch similar calls together

  • If you hit TPM: Your max_tokens value may be too high — each request reserves its full max_tokens against your TPM allowance while in flight


Need More Help?

Last updated

Was this helpful?