main.js · part 247

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

File contents and all parts · All files

Content to write to the file

Search pattern (regex or literal string)

Directory or file to search (default: current directory)

Filter files by glob pattern, e.g. '*.ts' or '**/*.spec.ts'

Case-insensitive search (default: false)

Treat pattern as literal string instead of regex (default: false)

Number of lines to show before and after each match (default: 0)

Maximum number of matches to return (default: 100)

Glob pattern to match files, e.g. '*.ts', '**/*.json', or 'src/**/*.spec.ts'

Directory to search in (default: current directory)

Maximum number of results (default: 1000)

Directory to list (default: current directory)

Maximum number of entries to return (default: 500)

Pi tool returned no result.

Unknown Pi tool error

Read the contents of a file using pi-compatible semantics.

Unknown Pi_read result

Unknown Pi_read result

Unknown Pi_read result

Execute a bash command using pi-compatible output and timeout semantics.

Unknown Pi_bash result

Edit a single file using pi-compatible exact text replacements.

Unknown Pi_edit result

Write content to a file using pi-compatible semantics.

Unknown Pi_write result

Search file contents for a pattern using pi-compatible grep semantics.

Unknown Pi_grep result

Search for files by glob pattern using pi-compatible find semantics.

Unknown Pi_find result

List directory contents using pi-compatible flat listing semantics.

Unknown Pi_ls result

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Expected repository in 'owner/name' form

Optional repository in 'owner/name' form that the user wants connected. Provide it when the user named a specific repo so the connect flow can also prompt to install the app there.

When user is blocked on connecting to GitHub.

Offer the user a Connect GitHub prompt when source-control access would unblock the task, such as reviewing pull requests, opening pull requests, or acting on a repository. The user may connect, skip, or the attempt may fail. Offer this on your own initiative at most once per conversation; after a skip or failure, don't re-offer it unless the user explicitly asks to use ${cH(e.allTools)}. Otherwise report what happened and continue without GitHub.

User skipped connecting GitHub

Failed to connect GitHub

Successfully connected the user's GitHub account. Source-control-dependent features (such as PR review) are now available.

Connecting GitHub timed out

Connecting GitHub was canceled

GitHub could not be connected: ${r}. Report the failure and continue without GitHub for this conversation.${n?` The user may still be completing authorization in their browser; if they later say they finished connecting, call ${t} again to re-check (it completes instantly when the connection exists).`:` If the user says they have connected GitHub since, call ${t} again to re-check (it completes instantly when the connection exists).`}

 The user may still be completing authorization in their browser; if they later say they finished connecting, call ${t} again to re-check (it completes instantly when the connection exists).

 If the user says they have connected GitHub since, call ${t} again to re-check (it completes instantly when the connection exists).

The user chose to skip connecting GitHub. Don't offer again on your own; only call ${t} again if the user explicitly asks. Continue without GitHub for now.

Unknown error while connecting GitHub

Unhandled result case: ${String(t)}

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Absolute repository path for this branch update.

New active branch name.

Set active git branch metadata for the current conversation and client UI. This directly controls which merge-base diff and related pull requests are shown to the user. Call this tool immediately when you are making changes on an existing feature branch, and call it immediately after committing changes to a new branch.

Active branch updated.