# Troubleshooting > Fixes for the common problems: the chat can't see Speed's tools, no tab is connected, another tab took over, sign-in, approvals, declined requests, timeouts and blocked connectors. Source: https://tryspeed.ai/docs/troubleshooting ## The chat can't see Speed's tools The chat says it has no Speed tools, or it doesn't call them. 1. **claude.ai or Claude Desktop:** in the chat, click **+** (bottom left) → **Connectors** and check **Speed** is switched on. 2. Tools are loaded when a chat starts. **Start a new chat** with Speed switched on, and paste [the Speed prompt](https://tryspeed.ai/docs/prompt.md) again. 3. Check the connector is connected: **Customize → Connectors** (older versions: **Settings → Connectors**) should show Speed as connected. If it shows **Connect**, click it and click **Allow**. 4. **Claude Code:** type `/mcp`. Speed should be listed as connected. If it says it needs authentication, choose **speed → Authenticate**. If Speed is missing, run the [add command](https://tryspeed.ai/docs/connect.md#claude-code) again and restart Claude Code. ## No Speed tab is connected The chat says no Speed tab is connected and sends you a link. 1. Open the link the chat sent (it is `https://app.tryspeed.ai/?agent=connect`). 2. Open it in any browser. The link carries this chat's connection, so the tab connects by itself, even in a different browser from the one you clicked Allow in. 3. Sign in if Speed asks. When the tab is ready, the bar at the top of the canvas says **Connected to Claude**. 4. Tell the chat `done`. It checks again and carries on. Keep that tab open while the chat builds. If you close it, ask the chat for the link again. ## The tab says another tab took over One Speed tab works for the chat at a time. The tab you opened the chat's link in (or pressed **Use this tab** in) is the live one. Other Speed tabs in the same browser stay on standby and never take a build over by themselves. 1. Pick the tab you want to keep and close the other one. 2. If the tab you kept doesn't show **Connected to Claude**, reload it. 3. Ask the chat to carry on. ## Sign-in problems - Speed accepts **Continue with Apple**, a sign-in link sent to your work email, or an access code. Use the same one on the **Connect Speed** page and in the Speed tab. - No email? Check your spam folder and wait a minute before asking for another link. - No access yet? Ask at [tryspeed.ai/contact](https://tryspeed.ai/contact). - If the **Connect Speed** page loops back to sign-in, allow cookies for app.tryspeed.ai and try again. ## A step timed out A single tool call that takes longer than 280 seconds times out in the chat. The work often finishes in the Speed tab anyway, especially large FE reports. 1. Look at the Agent panel in Speed. Wait until the last step finishes. 2. Ask the chat: `Call status and show me where we are.` It reads the design as it is now. 3. For big FEA runs, ask for one load case at a time, or for `run_fea` instead of the full FE report. ## A download link doesn't work - Download links last one hour. Ask the chat to make the file again for a fresh link. - Exported files larger than about 3 MB fail. Open the drawings or report in the Speed tab instead. ## Connect fails or keeps asking 1. Remove Speed from your AI app's connectors and add it again with the URL exactly as shown: `https://app.tryspeed.ai/mcp`. 2. Don't fill in an API key, client ID, client secret or header. Speed needs none. 3. In Claude, the sign-in settings should be **Sign in now** with OAuth client **Register automatically**. Claude detects these by itself; if you changed them, set them back. ## My workspace blocks custom connectors Company workspaces often let only admins add connectors. - **Claude Team or Enterprise:** an Owner adds Speed under **Organization settings → Connectors**. Then you click **Connect** on it. See [the Claude steps](https://tryspeed.ai/docs/connect.md#claude). - **ChatGPT Business, Enterprise or Edu:** an admin may have to allow custom MCP servers. - **Cursor, VS Code and Windsurf:** admins can restrict MCP servers to an allowlist. - Send your admin the URL `https://app.tryspeed.ai/mcp` and a link to [Limits, privacy and safety](https://tryspeed.ai/docs/limits.md) so they can see what is shared. ## Claude asks before every step Claude stops and asks you to approve each Speed tool call. 1. Go to **Customize → Connectors** and open **Speed**. 2. Under **Tool permissions**, set **Read-only tools** and **Write/delete tools** to **Always allow**. 3. Ask the chat to carry on. Every change is still one undo step in Speed, and **Pause** in the Speed tab still stops it. ## The chat declined part of my request AI models decline to design weapons, or parts whose purpose is to disable or bring down aircraft or harm people. For example, Claude will design a counter-drone **detection** system but not the part that knocks drones down. - Ask for the sensing or supporting system instead: detection and tracking, the airframe, a sensor mast, a gimbal, optics, the structure, mounts, power or an enclosure. - For example, instead of "a drone blocker that knocks drones down", ask for "a counter-drone detection mast with a direction-finding antenna, solar power and a battery". See [the detection mast example](https://tryspeed.ai/docs/examples/drone-detection-mast.md). - Read [What the chat won't design](https://tryspeed.ai/docs/limits.md#what-the-chat-wont-design) for the full list. ## Stop the chat working - **Pause** in the bar at the top of the Speed canvas stops further tool calls until you resume. - **Disconnect** ends the connection between this tab and the chat. - **Undo** takes back the chat's changes one step at a time.