daemon.cjs · part 242

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

File contents and all parts · All files

Executing computer action

Unexpected result case: ${execResult.result.case}

Use a mouse and keyboard to interact with a computer screen. This is an interface to a desktop GUI. After actions, a screenshot will be returned.

use strict

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

use strict

use strict

use strict

Perform manual testing of built applications and code. This subagent has access to the computer and browser to test the application. This subagent_type is stateful; if a computerUse subagent already exists, the previously created subagent will be resumed if you reuse the Task tool with subagent_type set to computerUse.

use strict

Enter COMPUTER USE mode. Follow the provided instruction above.

Debug Mode Logging Instructions

STEP 1: Understand the logging configuration

**Log file path:** `

Logs are written in **NDJSON format** (one JSON object per line)

You do not need to pre-create the log file; it will be created automatically when your instrumentation first writes to it

STEP 2: Understand the log format

Example log entry format:

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

STEP 3: Insert instrumentation logs

For **all languages**, instrument by opening the log file in append mode using standard library file I/O, writing a single NDJSON line with your payload, and then closing the file. Keep these snippets as tiny and compact as possible (ideally one line, or just a few).

**JavaScript/TypeScript example:**

**Python example:**

import json,os; open(os.path.expanduser('${DEBUG_LOG_PATH}'),'a').write(json.dumps({"location":"file.py:LINE","message":"desc","data":{},"timestamp":0,"hypothesisId":"A"})+'\n')

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}`

**REQUIRED:** Wrap EACH debug log in a collapsible code region:

Use language-appropriate region syntax (e.g., `// #region agent log`, `// #endregion` for JS/TS)

This keeps the editor clean by auto-folding debug instrumentation

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

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

Use the `Delete` tool to delete the file at `

` before reproduction

If `Delete` is unavailable or fails: instruct the caller to manually delete the log file

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

Do NOT use shell commands (rm, touch, etc.); use the `Delete` tool only

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

STEP 5: Read logs after reproduction

After the caller reproduces the issue and confirms completion, use the file-read tool to read the file at `

The log file will contain NDJSON entries (one JSON object per line) from your instrumentation

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

If log file is empty or missing: tell the caller the reproduction may have failed and ask them to try again

STEP 6: Keep logs during fixes

When implementing a fix, DO NOT remove debug logs yet

Logs MUST remain active for verification runs

You may tag logs with `runId="post-fix"` to distinguish verification runs from initial debugging runs

**FORBIDDEN:** Removing or modifying any previously added logs in any files before post-fix verification logs are analyzed or explicit confirmation of success

Only remove logs after a successful post-fix verification run (log-based proof) or explicit confirmation that the issue is fixed