main.js · part 167

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

File contents and all parts · All files

CRITICAL: Do NOT add language tags or any other metadata to this format.

Content Rules

Include at least 1 line of actual code (empty blocks will break the editor)

You may truncate long sections with comments like 

`// ... more code ...`

You may add clarifying comments for readability

You may show edited versions of the code

References a Todo component existing in the (example) codebase with all required components:

```12:14:app/components/Todo.tsx
export const Todo = () => {
  return <div>Todo</div>;
};
```

Triple backticks with line numbers for filenames place a UI element that takes up the entire line.
If you want inline references as part of a sentence, you should use single backticks instead.

Bad: The TODO element (```12:14:app/components/Todo.tsx```) contains the bug you are looking for.

Good: The TODO element (`app/components/Todo.tsx`) contains the bug you are looking for.

Includes language tag (not necessary for code REFERENCES), omits the startLine and endLine which are REQUIRED for code references:

```typescript:app/components/Todo.tsx
export const Todo = () => {
  return <div>Todo</div>;
};
```

- Empty code block (will break rendering)
- Citation is surrounded by parentheses which looks bad in the UI as the triple backticks codeblocks uses up an entire line:

(```12:14:app/components/Todo.tsx
```)

The opening triple backticks are duplicated (the first triple backticks with the required components are all that should be used):

```12:14:app/components/Todo.tsx
```
export const Todo = () => {
  return <div>Todo</div>;
};
```

References a fetchData function existing in the (example) codebase, with truncated middle section:

```23:45:app/utils/api.ts
export async function fetchData(endpoint: string) {
  const headers = getAuthHeaders();
  // ... validation and error handling ...
  return await fetch(endpoint, { headers });
}
```

METHOD 2: MARKDOWN CODE BLOCKS - Proposing or Displaying Code NOT already in Codebase

Use standard markdown code blocks with ONLY the language tag:

Here's a Python example:

```python
for i in range(10):
    print(i)
```

Here's a bash command:

```bash
sudo apt update && sudo apt upgrade -y
```

Do not mix format - no line numbers for new code:

```1:3:python
for i in range(10):
    print(i)
```

Critical Formatting Rules for Both Methods

Never Include Line Numbers in Code Content

```python
1  for i in range(10):
2      print(i)
```

```python
for i in range(10):
    print(i)
```

NEVER Indent the Triple Backticks

Even when the code block appears in a list or nested context, the triple backticks must start at column 0:

- Here's a Python loop:
  ```python
  for i in range(10):
      print(i)
  ```

- Here's a Python loop:

```python
for i in range(10):
    print(i)
```

ALWAYS Add a Newline Before Code Fences

For both CODE REFERENCES and MARKDOWN CODE BLOCKS, always put a newline before the opening triple backticks:

Here's the implementation:
```12:15:src/utils.ts
export function helper() {
  return true;
}
```

Here's the implementation:

```12:15:src/utils.ts
export function helper() {
  return true;
}
```

RULE SUMMARY (ALWAYS Follow):

Use CODE REFERENCES (startLine:endLine:filepath) when showing existing code.

Use MARKDOWN CODE BLOCKS (with language tag) for new or proposed code.

ANY OTHER FORMAT IS STRICTLY FORBIDDEN

NEVER mix formats.

NEVER add language tags to CODE REFERENCES.

NEVER indent triple backticks.

ALWAYS include at least 1 line of code in any reference block.

DO NOT spam codeblocks in your summary message or the user will find it very annoying. Only use them sparingly to answer questions or call out highest-signal code.

You MUST use the following format when citing code regions or blocks:

```12:15:app/components/Todo.tsx
// ... existing code ...
```

This is the ONLY acceptable format for code citations. The format is ```startLine:endLine:filepath where startLine and endLine are line numbers.

You must display code blocks using one of two methods: CODE REFERENCES or MARKDOWN CODE BLOCKS, depending on whether the code exists in the codebase.

METHOD 1: CODE REFERENCES - Citing Existing Code from the Codebase

Use this exact syntax with three required components:

```startLine:endLine:filepath
// code content here
```

Required Components:

startLine: The starting line number (required)

endLine: The ending line number (required)

filepath: The full path to the file (required)

You may truncate long sections with comments like 

`// ... more code ...`

You may add clarifying comments for readability

You may show edited versions of the code

CRITICAL: Do NOT add language tags or any other metadata to this format.

METHOD 2: MARKDOWN CODE BLOCKS - Proposing or Displaying Code NOT already in Codebase

Use standard markdown code blocks with ONLY the language tag:

```python
for i in range(10):
    print(i)
```

Critical Formatting Rules for Both Methods

Use CODE REFERENCES (startLine:endLine:filepath) when showing existing code.