Skip to main content
This page covers the most common errors you may encounter while using Claude Scope, organized by where in the workflow they occur. For general questions about how the product works, see the FAQ.
If you are not sure where an error originates, open your browser’s developer console (F12 → Console) for detailed error messages from the recording client before reaching out for support.
The browser console also shows network errors when the upload or processing request fails — look for failed POST /recordings requests for upload issues, and WebSocket or polling errors for processing status issues.

​
Recording issues

When you click Start Recording, the browser displays a screen sharing permission dialog. If you dismiss it or click “Don’t allow,” the recording cannot start.To fix this:
  1. Click Start Recording again to re-trigger the permission dialog.
  2. If the browser blocked the permission permanently, go to your browser’s site settings (Chrome: Settings → Privacy and security → Site settings → Permissions → Camera / Screen recording) and reset the permission for the Claude Scope URL.
  3. Reload the page and try again.
By default, auto-stop is enabled and triggers at 30 seconds. If your recording ended earlier than you expected, auto-stop is the most likely cause.To record for longer:
  • On the recording setup screen, toggle off Auto-stop at 30 seconds before clicking Start Recording.
  • Alternatively, go to Settings and increase the maximum recording length to 5, 10, 15, or 30 minutes.
If the recording stopped because you accidentally clicked away from the browser tab sharing dialog, start a new recording and keep the dialog in focus until recording begins.
Uploaded files are limited to 100 MB. If your recording file exceeds this limit, you will see an upload error.To reduce file size:
  • Shorten the duration of your recording — keep it focused on the specific UI flow you want to document.
  • Lower your screen resolution before recording (e.g., record at 1280×720 instead of a higher resolution) to reduce per-frame data size.
  • The browser recorder produces WebM by default, which is more space-efficient than MP4 for screen content.

​
Processing errors

This error means the Anthropic API could not be reached or returned an error during frame analysis. The most common causes are a missing or invalid API key.To fix this:
  1. Go to workspace → Model Access and verify that your Anthropic API key is present and correct.
  2. Confirm you are using a model that supports image input: claude-3-5-sonnet, claude-3-opus, or claude-3-haiku.
  3. If the key looks correct, test it directly in the Anthropic Console to confirm it is active.
  4. Re-add the key in Model Access if needed, then start a new recording.
Claude Scope runs a Playwright-based browser on the backend to capture ARIA accessibility snapshots of your seed URL. This error means the backend processing service is temporarily unavailable.Wait a few minutes and start a new recording. If the error persists across multiple attempts, the service may be undergoing maintenance. Check the Claude Scope status page or community channels for updates.
This error occurs when every extracted frame was rejected by the Anthropic API. Unlike a partial failure, zero successful frames means the prompt cannot be generated.Common causes:
  • Insufficient API credits: Check your credit balance in the Anthropic Console.
  • Wrong model selected: The selected model may not support image inputs. Switch to claude-3-5-sonnet, claude-3-opus, or claude-3-haiku in Model Access and try again.
  • Rate limiting: If you have a low-tier Anthropic plan, a recording with many extracted frames may exceed your requests-per-minute limit. Try a shorter, more focused recording.

​
Output issues

If the Output page is empty or shows no prompt, the session may still be processing. Go to the Sessions page and check the status:
  • processing — the pipeline is still running; wait for it to complete and refresh.
  • error — processing failed; review the error message shown on the session and see the Processing errors section above.
  • complete — if the status is complete but the prompt is still missing, try refreshing the Output page. If the issue persists, start a new recording.
The generated prompt combines visual frame analysis with ARIA structural data. If the prompt seems to be missing UI structure detail, try the following:
  • Enable Inline ARIA tree in the output options — this embeds the full accessibility tree directly into the prompt rather than summarizing it.
  • Confirm the seed URL you entered in the recording setup was the exact page URL you wanted inspected. If the URL was incorrect or unreachable, the Playwright inspection will have captured no data, leaving the structural section of the prompt empty.
  • If the recording was very short, only one or two frames may have been extracted, giving the vision lane limited material to work with. Record a slightly longer interaction to capture more UI state transitions.

​
Account issues

This error means your authentication session has expired or become invalid. Refresh the page — you will be redirected to the sign-in screen. Sign in again to restore access. Your sessions and recordings are not affected by signing out.
Claude Scope stores your Anthropic API key in browser localStorage. Clearing your browser’s cookies and site data removes the key along with all other locally stored data.If your key has disappeared:
  1. Go to workspace → Model Access.
  2. Re-enter your Anthropic API key.
  3. To avoid losing it again, avoid clearing site data for the Claude Scope domain, or save your API key securely in a password manager.