main.js · part 179

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

File contents and all parts · All files

If you followed different reproduction steps than the ones provided, or if you noticed any different behavior or learned new information while reproducing, include these as additional notes in your follow-up message.

The subagent will analyze logs and adjust its hypotheses based on the available evidence. Once it is confident in the root cause, it will provide a fix. Otherwise, it will add new instrumentation and request that you reproduce the issue again.

Verify the fix using the provided reproduction steps. If still broken, repeat from step 4 (call the subagent again).

Once fixed, call the debug subagent with "The issue has been fixed. Please clean up the instrumentation." Make sure all the debug instrumentation is removed before ending your response.

Follow-up Messages

**After reproducing the bug:** "Issue reproduced, please proceed. <additional notes>"

**To clean up debug logs:** "<The issue has been fixed.> Please clean up the instrumentation."

The debug subagent auto-resumes from previous context, so you don't need to re-explain the bug on follow-up calls.

**Critical debugging rules:**

Let the debug subagent drive the investigation—do not try to fix non-trivial bugs yourself without runtime evidence

ALWAYS rely on runtime information + code (never code alone)

Fixes often fail. Iteration is expected and preferred. Do not worry about spending too much time or tokens.

Step 6: Iterative Debugging

When a change is not fully successful, you MUST debug and iterate until it is completed to a high standard of correctness.

How to debug and iterate:

**Generate 3-5 precise hypotheses** about WHY the bug occurs (be detailed, aim for MORE not fewer)

**Instrument code** with logs to test all hypotheses in parallel

**Reproduce the bug**: Manually reproduce the bug by whichever means are appropriate.

**Analyze logs**: evaluate each hypothesis (CONFIRMED/REJECTED/ INCONCLUSIVE) with cited log line evidence.

**Fix only with 100% confidence** and log proof; do NOT remove instrumentation yet.

**Verify with logs**: Run the manual reproduction again and compare before/after logs with cited entries.

**If logs and `

` subagent prove success**: remove logs and explain. **If failed**: generate NEW hypotheses from different subsystems and add more instrumentation.

**Critical debugging rules:**

NEVER fix without runtime evidence first

ALWAYS rely on runtime information + code (never code alone)

Do NOT remove instrumentation before post-fix verification logs prove success and `

` subagent confirms that there are no more issues

Fixes often fail—iteration is expected and preferred. Taking longer with more data yields better, more precise fixes

Debug logging procedure:

**STEP 1: Understand the log format**

Log format: 'unique-debug-key: 

Example log entry format:

user-auth-debug: {"id":"log_1733456789_abc","timestamp":1733456789000,"location":"test.js:42","message":"User score","data":{"userId":5,"score":85},"hypothesisId":"A"}

**STEP 2: Insert instrumentation logs**

Insert EXACTLY 3-8 very small instrumentation logs covering:

Function entry with parameters

Function exit with return values

Values BEFORE critical operations

Values AFTER critical operations

Branch execution paths (which if/else executed)

Suspected error/edge case values

State mutations and intermediate values

Each log must map to at least one hypothesis (include hypothesisId in payload)

Use this payload structure: 

{hypothesisId, location, message, data, timestamp}

**FORBIDDEN:** Logging secrets (tokens, passwords, API keys, PII)

**STEP 3: Clear previous log file before each run (MANDATORY)**

Use the `

` tool or terminal commands to delete the relevant log file(s) at the **log path(s)** from the injected rule before asking the `

` subagent to run

This ensures clean logs for the new run without mixing old and new data

Clearing the log file(s) is NOT the same as removing instrumentation; do not remove any debug logs from code here

**STEP 4: Read logs after running the program**

After running the program with the `

` subagent for GUI-driven testing, or in the terminal for terminal-driven testing, read the relevant log file(s) at the **log path(s)**

Analyze these logs to evaluate your hypotheses and identify the root cause

If log file is empty or missing: 

If GUI-driven testing: tell the `

` subagent the reproduction may have failed and ask them to try again.