automatelab/automation-error-index huggingface dataset:
Platform: AutoGen
Category: version
Error: ValueError: Message type StructuredMessage[AgentResponse] is not registered.
Affected versions: autogen-agentchat>=0.6.4
Cause: Since autogen-agentchat 0.6.4 the Teams integration changed message-type registration; agents using output_content_type add custom StructuredMessage subtypes never registered with the group-chat container, so logging raises ValueError.
Fix: Downgrade to autogen-agentchat==0.6.2 as a temporary workaround. Remove output_content_type from affected agents if the structured type is not strictly required. Watch issues #6795 and #6983 for an official patch that registers custom message types at group-chat init.
Platform: AutoGen
Category: config
Error: Failed to instantiate component: model_info is required when model name is not a valid OpenAI model
Affected versions: autogen-studio==0.4.2
Cause: AutoGen cannot infer capabilities for non-standard identifiers (Azure deployment names, local models), so it requires an explicit model_info dict when the name does not match a known OpenAI slug.
Fix: Add a model_info dict specifying capabilities (e.g. {"vision": false, "function_calling": true, "json_output": true}). For Azure OpenAI, pair the deployment name with the matching model_info for the underlying model. See the AutoGen ModelInfo dataclass for required keys.
Platform: AutoGen
Category: config
Error: TypeError: create() takes 1 argument(s) but 2 were given
Affected versions: autogen-ext==0.4.5
Cause: MagenticOneGroupChat passes chat.completions from the standard OpenAI client to create(), but the AsyncAzureOpenAI wrapper uses a different signature that rejects the extra positional argument.
Fix: Pass an AzureOpenAIChatCompletionClient (from autogen_ext.models.openai) instead of extracting service_client.chat.completions directly. Construct it with azure_deployment, azure_endpoint, and api_version. Do not mix the raw Azure OpenAI SDK client with MagenticOne components.
Platform: Claude Code
Category: other
Error: Failed to Connect
Cause: If curl reaches your HTTP MCP server but Claude Code reports "Failed to connect," the CLI's Bun runtime is failing to open the socket - switch to a stdio or SSE transport, or run the server through the VS Code...
Platform: Claude Code
Category: install
Error: spawn npx ENOENT
Cause: On Windows, npx is a batch shim that bare spawn can't find - change command to cmd with args ["/c","npx"] to fix spawn npx ENOENT ; for spawn uv ENOENT run winget install astral-sh.uv then use the full path Both...
Platform: Claude Code
Category: other
Error: claude mcp add: unknown option --command
Cause: There is no --command flag in claude mcp add ; for stdio servers the command goes after a -- separator, and all options like --transport and --scope must come before the server name, not after it
Platform: Claude Code
Category: install
Error: No available IDEs detected
Cause: When /ide in Claude Code reports "No available IDEs detected" while Cursor is open on the Windows host but Claude Code is installed inside WSL, relaunch Cursor from inside WSL with cursor
Platform: Claude Code
Category: other
Error: Claude Code creating a 'nul' file on Windows
Cause: If Claude Code keeps dropping a file named nul in your Windows project and Explorer or del nul refuses to remove it, the fix is two commands
Platform: Claude Code
Category: auth
Error: MCP Token expired without refresh token in Claude Code
Cause: Claude Code's "Token expired without refresh token" is bug #25245 ; delete the stale credential entry, re-authenticate via /mcp , and on macOS grant the Keychain item persistent access
Platform: Claude Code
Category: config
Error: Claude Code SessionStart hooks firing without context
Cause: If a Claude Code plugin's SessionStart hook fires successfully but Claude never sees the additionalContext (bug #16538), move the hook config out of the plugin's hooks.json and into ~/.claude/settings.json
Platform: Claude Code
Category: connectivity
Error: MCP servers failed to connect
Cause: An MCP server child process is aborted during initialization, often due to a missing API key in keychain or an init timeout before the server responds.
Fix: Verify your Anthropic API key is set and reachable. Test the MCP server binary directly in a terminal to confirm it starts within the timeout. Create the missing cache directory: mkdir -p ~/Library/Caches/claude-cli-nodejs. If the same config works in Claude Desktop, update Claude Code to the latest version (a known CLI-only bug).
Platform: Claude Code
Category: auth
Error: OAuth error: Failed to fetch user roles: OAuth account information not found in config
Cause: The OAuth flow completes in the browser but Claude Code fails to write or read back the token from the config file.
Fix: Full reinstall: npm uninstall -g @anthropic-ai/claude-code; rm -rf ~/.claude ~/Library/Application\ Support/ClaudeCode; npm cache clean --force; npm install -g @anthropic-ai/claude-code; then log in again.
Platform: Claude Code
Category: auth
Error: API Error: 401 authentication_error: Invalid bearer token
Error code: 401
Affected versions: 2.0.28
Cause: A regression in v2.0.28 made the stored bearer token invalid or unable to refresh, persisting across logout/login.
Fix: Run 'claude logout' then 'claude login' to force a new token. If it persists, remove ~/.claude/claude.json and any ANTHROPIC_AUTH_TOKEN/ANTHROPIC_BASE_URL env vars, reinstall with npm install -g @anthropic-ai/claude-code, and authenticate again.
Platform: Claude Code
Category: auth
Error: OAuth error: timeout of 15000ms exceeded
Affected versions: 2.1.72
Cause: DNS resolution for auth.anthropic.com fails in certain regions/networks, so the OAuth login request times out after 15 seconds.
Fix: Confirm auth.anthropic.com resolves with 'nslookup auth.anthropic.com 8.8.8.8'. If not, use a VPN or a different DNS server. Alternatively authenticate via API key by setting ANTHROPIC_API_KEY instead of the browser OAuth flow.
Platform: Claude Code
Category: install
Error: command not found: claude
Cause: On macOS with Homebrew-managed Node, npm creates a symlink pointing to the raw JS file rather than the executable launcher, so 'claude' is not on PATH.
Fix: Remove the broken symlink: rm /opt/homebrew/bin/claude. Create the correct one into the Cellar: ln -s /opt/homebrew/Cellar/node/<version>/bin/claude /opt/homebrew/bin/claude. Verify with 'claude --version'.
Platform: Claude Code
Category: install
Error: Claude Code is not supported on Windows. Claude Code requires macOS or Linux.
Cause: The npm preinstall script detects Windows when 'npm install' runs from a Windows-side path inside WSL, even though the shell is Linux.
Fix: Use a true WSL terminal (not PowerShell/CMD) and confirm 'uname -a' reports Linux. Ensure npm is the WSL-side binary ('which npm' under /usr/, not /mnt/c/). If npm is Windows-side, install Node natively in WSL (nvm install --lts), then reinstall: npm install -g @anthropic-ai/claude-code.
Platform: Claude Code
Category: install
Error: ENOEXEC: posix_spawn '/mnt/c/Windows/System32/reg.exe'
Error code: ENOEXEC
Affected versions: 2.1.108 2.1.118
Cause: Claude Code unconditionally spawns reg.exe on startup for Chrome native-messaging registration; with WSL Windows interop disabled, the file exists at the mount path but cannot execute.
Fix: If interop must stay disabled, there is no user-side fix as of v2.1.118 - the crash precedes any prompt. As a workaround, temporarily re-enable interop in /etc/wsl.conf ([interop] enabled=true) while launching Claude Code, then disable again. Track the upstream issue for a fix.
Platform: Claude Code
Category: other
Error: /usr/bin/bash: line 1: /c/Users/<name>: Permission denied
Cause: Claude Code builds a shell state-tracking command with an unquoted path; when the Windows username contains a space, Bash word-splits the path and tries to execute the first token.
Fix: Rename the Windows user to remove the space, or create a new account without a space and run Claude Code from it. Commands still execute correctly despite the error, so it is cosmetic until an upstream fix ships.
Platform: Claude Code
Category: other
Error: EACCES: permission denied, mkdir '/tmp/claude/<path>/tasks'
Error code: EACCES
Cause: Claude Code uses a shared /tmp/claude/ directory owned by the first user who ran it; other users lack write permission to create subdirectories.
Fix: Recreate with world-writable sticky bit: sudo rm -rf /tmp/claude && sudo mkdir -p /tmp/claude && sudo chmod 1777 /tmp/claude. Alternatively set dangerouslyDisableSandbox: true in .claude/settings.json as a temporary workaround.
Platform: Claude Code
Category: other
Error: zsh:1: permission denied: /var/folders/.../T/claude-XXXX-cwd
Cause: Claude Code writes a temporary CWD-tracking file to the system temp directory; after a macOS major upgrade the permissions change and block writes from user processes.
Fix: Bash commands still execute correctly - this is cosmetic. There is no user-side fix as the temp path is internal. Check for a newer Claude Code release that resolves it and follow the linked issue for a patch.
Platform: Claude Code
Category: config
Error: Stop hook error
Cause: Claude Code's hook output validator treats zero bytes of output as a missing JSON object and falsely reports a stop-hook failure, even when the hook exits 0.
Fix: Confirm the hook works by checking its exit code manually - the error is cosmetic for hooks that produce no output and exit 0. As a workaround, emit an empty JSON object from the hook: echo '{}'. Track the upstream fix in the linked issue.
Platform: Claude Code
Category: config
Error: [DEBUG] Found 0 hook matchers in settings
Cause: An extra 'hooks' wrapper object inside each event array makes the hook parser find no valid matchers and silently skip all hook execution.
Fix: Open ~/.claude/settings.json and remove the intermediate {"hooks": [...]} wrapper. Each event key should map directly to an array of hook objects. Run /hooks inside Claude Code to verify hooks are now listed.
Platform: Claude Code
Category: schema
Error: invalid_type expected string received undefined at path protocolVersion
Cause: Claude Code's MCP init layer drops the protocolVersion field before sending the initialize request to stdio servers, so schema validation fails before any data is sent.
Fix: Use a wrapper shell script instead of referencing the server directly: export MCP_PROTOCOL_VERSION=2025-03-26 and exec your server binary. Register the wrapper: claude mcp add <name> /path/to/wrapper.sh. This bypasses the internal validation step.
Platform: Claude Code
Category: connectivity
Error: Failed to reconnect to MCP server
Cause: Claude Code spawns MCP subprocesses with an unescaped working directory; when its launch directory contains spaces or special characters (e.g. iCloud Drive), spawning fails.
Fix: Launch Claude Code from a directory whose full path has no spaces or special characters: cd ~/Projects/myproject && claude. The MCP server's own cwd setting does not prevent this - the launch directory of Claude Code itself must be clean. Confirmed upstream bug with no config workaround.
Platform: Claude Code
Category: rate-limit
Error: API Error: Rate limit reached (stale cached plan after upgrade)
Error code: 429
Affected versions: 2.1.92
Cause: Claude Code caches subscriptionType and rateLimitTier at login and never refreshes them, so after a plan upgrade the CLI still enforces old limits.
Fix: Clear the accessToken, refreshToken, expiresAt, subscriptionType, and rateLimitTier fields in ~/.claude/.credentials.json, then run 'claude login' to force a fresh OAuth flow. Verify the correct plan shows in the CLI header before resuming.
Platform: Claude Code
Category: rate-limit
Error: API Error: Rate limit reached despite Max subscription and low usage
Error code: 429
Affected versions: 2.1.63
Cause: A corrupted credentials.json (subscriptionType and rateLimitTier both null) makes the CLI enforce API-tier limits even after a successful re-login that shows Max in the header.
Fix: Run 'claude logout', then delete or zero the subscriptionType and rateLimitTier fields in ~/.claude/.credentials.json. Run 'claude login' and confirm /status shows the correct tier and sane usage. If it persists, wait for the session reset window shown in the error.
Platform: CrewAI
Category: schema
Error: CrewAI hierarchical DelegateWorkToolSchema validation error
Cause: If a CrewAI crew running Process.hierarchical raises 2 validation errors for DelegateWorkToolSchema ..
Platform: CrewAI
Category: schema
Error: ValidationError: 1 validation error for Task - expected_output Field required
Affected versions: crewai>=0.19
Cause: The CrewAI Task model marks expected_output as required with no default; omitting it (or a Pydantic 2.8+ alias edge case) raises a ValidationError at instantiation.
Fix: Always pass an explicit expected_output string when constructing a Task. If the error appears even when present, pin pydantic<2.8 as a temporary workaround for the upstream alias-handling bug. Upgrade CrewAI once a patch is released.
Platform: CrewAI
Category: install
Error: AttributeError: _ARRAY_API not found; ImportError: numpy.core.multiarray failed to import
Cause: A transitive dependency (typically onnxruntime) was compiled against NumPy 1.x and cannot load under NumPy 2.x, which removed the legacy numpy.core namespace.
Fix: Downgrade NumPy with pip install 'numpy<2' as an immediate fix, or upgrade onnxruntime to a NumPy-2-compatible build. Check compiled deps with pip list | grep onnx and update any that predate NumPy 2 support.
Platform: CrewAI
Category: install
Error: click.exceptions.Abort: You are missing the 'mcp' package
Cause: MCPServerAdapter.__init__() calls click.confirm() interactively when the mcp package is absent, which aborts in non-TTY environments like FastAPI, Docker, and CI.
Fix: Install the package: pip install mcp crewai-tools[mcp]. In headless environments, ensure mcp is in your requirements file so MCPServerAdapter never reaches the prompt. Track the upstream fix (raise ImportError instead of prompting) in CrewAI issue #3163.
Platform: Cursor
Category: other
Error: Cursor's Terminal sandbox error on Linux (AppArmor)
Cause: Run sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 , then persist it in /etc/sysctl.d/99-cursor.conf - don't chmod the sandbox binary, that fix makes it worse
Platform: Cursor
Category: auth
Error: Cursor Override OpenAI Base URL Breaks Anthropic Key: Fix
Cause: Cursor's "Override OpenAI Base URL" toggle routes Anthropic key requests through the wrong endpoint; turn it off in Settings > Models > API Keys, confirm it stays off, restart Cursor, and start a new chat
Platform: Cursor
Category: connectivity
Error: the Cursor Provider Error that lasts for days
Cause: Most persistent Cursor Provider Error s come from a conflicting MCP server, not your network — disable all MCPs, switch from Auto to a named model, and sign out and back in before doing anything more disruptive
Platform: Cursor
Category: connectivity
Error: the Cursor Connection Error when the agent stops working
Cause: Most Cursor "Connection failed" errors in Agent mode fix with one change: switch HTTP Compatibility Mode to HTTP/1.1 in Settings > Network, restart, and if the error persists start a new chat session
Platform: Cursor
Category: timeout
Error: agent execution provider did not respond in time
Cause: Press Ctrl+Shift+P, run "Developer: Reload Window" -- and if that fails, escalate to "Restart Extension Host," CachedData clear, or a clean reinstall when the Output log shows a hash mismatch on cursor-agent-exec
Platform: Cursor
Category: other
Error: Waiting for extension host
Cause: Cursor's "Waiting for extension host" hang clears fastest with Ctrl+Shift+P â†’ "Developer: Restart Extension Host"; if that fails, launch with --disable-extensions , delete the state database, or update to the...
Platform: Cursor
Category: other
Error: Clear the Cursor Cache: Fix Stuck or Laggy AI
Cause: Clearing Cursor's cache fixes stuck indexing, frozen chat, and laggy autocomplete - quit Cursor and delete the Cache and CachedData folders under its app-data directory, or delete workspaceStorage to force a clean...
Platform: Cursor
Category: timeout
Error: Agent Execution Timed Out
Cause: After upgrading to Cursor 3, Jupyter notebooks refuse to open and the AI panel throws Agent Execution Timed Out because of a stale extension cache; delete %APPDATA%\Cursor\CachedExtensions and restart
Platform: Cursor
Category: other
Error: Cursor rules not loading: 4 causes and how to fix each
Cause: Cursor reads project rules from .cursor/rules/<name>.mdc at the repository root
Platform: Cursor
Category: rate-limit
Error: We've hit a rate limit with the provider. Please switch to the 'auto' model, another model, or try again in a few moments.
Cause: Cursor's upstream AI provider temporarily throttled requests due to high demand or plan-level throughput limits.
Fix: Switch the active model to 'auto' or a different model in the model picker. Wait 30-60 seconds and retry. If it persists, check your provider's usage dashboard for quota exhaustion. A higher Cursor/provider tier increases throughput.
Platform: Cursor
Category: rate-limit
Error: User API Key Rate limit exceeded
Cause: Cursor relays the rate-limit from the upstream provider when a BYOK key exhausts its requests-per-minute or token quota, which Agent mode can hit quickly via parallel tool calls.
Fix: Wait for the provider's rate-limit window to reset (usually 60s). Check your tier's RPM/TPM limits on the provider dashboard. In Settings > Models, reduce Agent concurrency or switch to a higher-quota model. Upgrade the provider tier if Agent workloads routinely hit the cap.
Platform: Cursor
Category: auth
Error: Authentication blocked, please contact your admin
Cause: The Auth0 sign-in flow detects a policy restriction - an org SSO/email-domain block, a school/work network firewall, or a flagged account - and rejects the attempt.
Fix: Try signing in with a personal email (Gmail/GitHub) not subject to the blocked domain. Allowlist cursor.com / auth.cursor.sh in corporate SSO or firewall settings. If a school/work email, ask IT to whitelist auth.cursor.sh. If the account is flagged, email hi@cursor.sh with the details.
Platform: Cursor
Category: other
Error: Codebase indexing failed
Cause: Background indexing cannot complete due to an oversized repo, a network/TLS failure, low disk space, or a corrupted local index cache.
Fix: Add large generated dirs (node_modules, dist, .git) to a .cursorignore. Ensure 5+ GB free disk. Run 'Cursor: Reindex Codebase' from the Command Palette. If it persists, close Cursor, delete the index cache (macOS ~/Library/Application Support/Cursor/User/globalStorage; Windows %APPDATA%\Cursor\User\globalStorage), and reopen.
Platform: Cursor
Category: connectivity
Error: Connection failed. If the problem persists, please check your internet connection or VPN
Cause: Cursor cannot reach its backend API servers, most often because a VPN, corporate proxy, or firewall is intercepting or blocking the TLS connection.
Fix: Disconnect the VPN and retry. In Settings search 'HTTP/2' and enable 'Disable HTTP/2', then restart. Behind a corporate proxy, set the proxy under Settings > Network Proxy and whitelist api2.cursor.sh. Check Cursor's status page for incidents.
Platform: Cursor
Category: other
Error: Your conversation is too long. Please try creating a new conversation or shortening your messages
Cause: The accumulated tokens in the current chat (files, tool outputs, history) exceeded the model's context window.
Fix: Start a fresh chat (Cmd/Ctrl+N) and reference only the needed files. Remove large @file/@codebase attachments no longer relevant. Break long multi-step tasks into separate chats. If it fires in a new chat, check no very large files are auto-attached via .cursorrules.
Platform: Cursor
Category: other
Error: The agent execution provider did not respond within 4 seconds. The extension host may be unresponsive.
Cause: Cursor's extension host process stops responding - often after an update or on resource-constrained machines - preventing the Agent from invoking tools.
Fix: Run 'Developer: Restart Extension Host' from the Command Palette. If that fails, quit and relaunch Cursor. Run 'cursor --disable-extensions' to isolate a crashing third-party extension. If still broken, reinstall from cursor.com/downloads (partial-update corruption).
Platform: Cursor
Category: version
Error: Please update to the latest version of Cursor at cursor.com/downloads to continue using the Agent
Cause: Cursor's backend enforces a minimum client version; older builds lack the API surface current agent tooling needs and are blocked from new Agent sessions.
Fix: Download and install the latest release from cursor.com/downloads, then fully restart. If auto-update is stuck, manually download the installer and run it over the existing installation.
Platform: Cursor
Category: auth
Error: The model does not work with your current plan or API key
Cause: The selected model is restricted to a higher tier, usage-based billing is off, or a BYOK key is routed through an incorrect base URL.
Fix: In Settings > Models, select a model your plan supports (free tier excludes several frontier models). Under API Keys, disable 'Override OpenAI Base URL' if enabled (it breaks Anthropic key routing). Enable usage-based billing for on-demand premium models. Verify the BYOK key is in the correct provider field.
Platform: Cursor
Category: other
Error: We encountered an issue when using your API key: Provider was unable to process your request
Cause: The provider rejected the request at the API level - typically because 'Override OpenAI Base URL' is enabled while using an Anthropic key, sending a malformed request to the wrong endpoint.
Fix: In Settings > Models > API Keys, turn off 'Override OpenAI Base URL'. Confirm the key is in the correct provider field with no whitespace. Test the key independently (curl or the provider playground) to rule out a revoked/quota-exhausted key. If a 400, confirm the model name is one the key's org can access.
Platform: Cursor
Category: auth
Error: Error: invalid api key provided
Cause: The stored API key is malformed, contains invisible whitespace from a browser copy, has been revoked, or is in the wrong provider field.
Fix: Delete the key in Settings > Models > API Keys and retype/paste it as plain text from the provider dashboard, with no leading/trailing spaces or newlines. Verify the key is active and not revoked. Ensure it is in the field matching its provider (Cursor has separate inputs per provider).
Platform: Cursor
Category: connectivity
Error: AI features broken: ECONNRESET stuck on local proxy 127.0.0.1
Error code: ECONNRESET
Cause: Cursor's traffic is intercepted by a local proxy (Clash, v2ray) on localhost that resets the TCP connection, blocking all AI API calls.
Fix: Pause or exit the local proxy and restart Cursor to test recovery. In Settings, enable 'Disable HTTP/2' and restart. If the proxy is required, point Cursor's network proxy setting at the correct address rather than relying on system-wide interception. Check the proxy logs for TLS inspection/cert pinning blocking Cursor.
Platform: Cursor
Category: auth
Error: Bad User API key / Unauthorized User API key
Cause: The 'Override OpenAI Base URL' toggle routes Anthropic API requests through OpenAI's endpoint, so auth fails even with a valid key.
Fix: Go to Settings > Models > API Keys and turn OFF 'Override OpenAI Base URL'. Restart Cursor, open a new chat, select a Claude model, and retry. If the toggle re-enables, disable it again and confirm it stays off before each session.
Platform: Cursor
Category: config
Error: This model does not support tools. Please select a different model and try again
Affected versions: 1.2.2
Cause: Agent mode routed a request to a model (e.g. o3) that does not expose a tool-calling API, often triggered automatically after the previous model hit a usage limit mid-session.
Fix: Restart Cursor to clear the stale model assignment. If it recurs, open Settings > Models and explicitly select a tool-capable model (claude-3-7-sonnet, gpt-4o) before starting an agent session. Avoid relying on automatic model fallback near usage limits.