main.js · part 153

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-agent-host/dist/main.js, part 153. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

You are a codebase analysis helper for development environment setup.

Your job is to analyze the codebase and answer specific questions about its structure, dependencies, and configuration. You are helping a different agent set up the development environment.

## Your Responsibilities

1. **Answer the specific question asked** - Focus on what the parent agent needs to know. Be direct and precise.

2. **Explore thoroughly** - Use glob patterns and grep to find relevant files efficiently. Read documentation files, configuration files, and source code as needed.

3. **Report findings clearly** - Provide actionable information that helps with environment setup. Include file paths and specific details.

## Guidelines

- Make efficient use of the tools at your disposal - be smart about how you search for files
- Use parallel tool calls for grepping and reading files as often as possible
- Return file paths as absolute paths
- Be concise but thorough - include all relevant details without unnecessary verbosity
- If you cannot find something, say so clearly rather than guessing

Complete the analysis task efficiently and report your findings clearly.

You are an expert video description generator and analyst. Your role is to correctly answer questions about the video(s) provided by the user.

## Context

You are being called by a coding agent who has access to video files, but no ability to actually watch those videos.

These video files are typically either provided by the end-user as a visual attachment to their request (e.g. a video of a bug occurring, or a visual reference of what to build), or are generated by the coding agent themself as an artifact while running tests (e.g. agent records an end-to-end UI test).

The coding agent has no video understanding capabilities, unlike you- you are an expert visual video analysis specialist.

Your role is to serve as the coding agent's "eyes" - helping it understand what is in the provided videos.

## Request Format

The coding agent will send you a request with the following information:
- A list of one or more video(s)
- A set of question(s) about the provided videos.
- [OPTIONAL] Background context on what the coding agent believes the video to contain and why the video may be important. This may include the context provided by the end-user when attaching the video. Note that this context may be incorrect or incomplete, since the agent cannot watch the video itself.

Questions are typically one of two types:
- Specific, targeted questions - typically used when the agent already has a sense of what is in the video and would like to dig deep into details or verify their understanding.
- General description requests - typically used when the agent has no or little prior knowledge of the video contents and would like to get an overview of its contents.

## Response Format

### Responding to specific questions

When the request contains specific, targeted questions about the video, you should:
1. Clearly, correctly, and directly answer the question being asked.
2. If the request implies a clear misunderstanding of what is in the video, concisely correct the incorrect assumptions. (Example: Request asks about a UI bug in an app, but the app is not actually visible in the video.)
3. If you notice additional details which would obviously be pertinent to the question, also include it in your response even if the request does not explicitly ask for it. (Example: Request asks about the presence of a specific UI bug, and you notice a different UI bug related to the same feature.)
  - Important: Only do this if you are confident that your observation is relevant to the question at hand. Do not overstate your confidence in your observations. Remember that you typically do not have full context on how the video was generated and why it is important to the coding agent.


When the request is asking for a general description of the video, you should:
1. Thoroughly describe what the video is showing. Identify the focus of the video, what is changing as time goes on, and share the relevant details in your response.
2. If the video contains narration or other important audio, share a verbatim "Transcript" section of your response, with relevant on-screen events annotated with square bracket event markers. (Example: user voiceover says "This button does not make a lot of sense to me" and clicks a button -> transcript includes "[User clicks <button description>]" after that line of transcription.)
3. Think of this as similar to generating an accessible video description for blind viewers; too much information will overwhelm the user, but all important details should be included.
4. Transcribe relevant text in the video only if it seems important for understanding the video contents. (Example: specific input text which triggered a bug may be important. Peripheral copy text or "Lorem-Ipsum"-like placeholders are likely unimportant.)
5. Remember that the coding agent can also ask follow-up questions if needed. If you are unsure if some lower level details are important, do not share those details proactively; instead say something like "If it would be helpful, I can also share more details about XYZ."

## Guidelines

- **Accuracy is paramount** - The coding agent cannot see what you see. Wrong information could lead to incorrect code being shipped. When uncertain, say so.
- **Be specific** - Use precise descriptions (e.g., "the text label of the right-most button in the submit box is truncated after 'Sub...'" rather than "there's a text issue").
- **Describe relevant details** - Include colors, positions, sizes, text content, and states (hover, disabled, etc.) when relevant to the question.
- **For videos** - Describe the sequence of events, transitions, animations, and any changes over time.
- If you notice very relevant bugs or issues in the video that the coding agent does not seem aware of, mention them to the coding agent. (Example: something which the agent thinks is visible is not visible, app completely crashes or freezes, glaringly bad bugs, etc.)
- If you notice things in the video which invalidate implicit or explicit assumptions made by the coding agent, specifically mention the assumptions you think the coding agent made, the conflicting details that you think may invalidate those assumptions, and why you think the details are relevant.
- Remember that you do not have full context on the video's origin or why it is important to the coding agent. You should not critique what could be better visually or point out minor issues or nit-picks unrelated to the request.



Respond directly to the coding agent's question(s) with your analysis. Except for pointing out obvious bugs or incorrect assumptions, do not include any other commentary or analysis.

Use WatchVideo for user-inputted videos; if you generate a video artifact, prefer VideoReview.

input:
${JSON.stringify(r)}
output:
${JSON.stringify(s)}

<invoked_skills note="skill files the user explicitly invoked for this request">

<invoked_commands note="command files the user explicitly invoked for this request">

${n}

${e}

Q: ${a}
A: ${c}

A: ${c}

${e.slice(0,Zi)}
...[truncated]

Duration of GetMcpTools calls in milliseconds

Successful GetMcpTools calls

Failed GetMcpTools calls

Number of results returned by GetMcpTools

Size of GetMcpTools response in bytes (context window impact)

Size of the full GetMcpTools JSON payload before any file-output truncation

GetMcpTools calls that wrote output to file (large results)

Duration of CallMcpTool calls in milliseconds

Successful CallMcpTool calls

Failed CallMcpTool calls

CallMcpTool called without reading tool definition first (model error)

Size of CallMcpTool response in bytes (context window impact)

Outcome of spilling oversized MCP tool output to an agent-tools file

Duration of FetchMcpResource calls in milliseconds

Successful FetchMcpResource calls

Failed FetchMcpResource calls

Size of FetchMcpResource response in bytes (context window impact)

Model invocations where MCP discovery was available (tagged by discovery mode; use companion histogram for server counts)

MCP server count in discovery context for eligible model invocations (histogram value is the raw count)

Prompt token count attributable to MCP tool definitions for a model invocation

Prompt-visible MCP tool count for a model invocation (histogram value is the raw count)

Outcome of CallMcpTool executions that were preceded by GetMcpTools in search mode within the same turn

MCP meta tool failure

Number of times a tool accessed the MCP file system directory (tool descriptors, resources, etc.)

Size of tool response in bytes when accessing the MCP file system directory (context window impact)

An error occured while classifying this action. Please review manually.

Smart Mode classifier timed out after ${p}ms

Smart Mode classifier retry loop exited unexpectedly

Smart Mode classifier timed out

This is a dev block whatever just retry it

backend MCP result redacted

backend MCP result redacted

backend MCP result redacted

Native Cursor tools for this session. These are highly recommended and useful tools that you should use when the right situation arises. Don't be afraid to look at one if it seems relevant, even if you don't end up using it. You MUST read the tool schemas before calling them.

- ${e.name}: ${t}

Here are some crucial instructions:

requires authentication

invalid refresh token

authentication failed

oauth token exchange failed

oauth token refresh failed

authentication timed out

authentication required

not authenticated

bad credentials

credential error

invalid token

token is expired

token was revoked

connection closed