main.js · part 237

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

File contents and all parts · All files

- User: "How does the auth system work?" → Switch to Ask (explanation only)
- User: "What files handle routing?" → Switch to Ask (exploration only)
- User: "Don't change anything, just explain this" → Switch to Ask

Switch the interaction mode to better match the current task. Each mode is optimized for a specific type of work.

## When to Switch Modes

Switch modes proactively when:
1. **Task type changes** - User shifts from asking questions to requesting implementation, or vice versa
2. **Complexity emerges** - What seemed simple reveals architectural decisions or multiple approaches
3. **Debugging needed** - An error, bug, or unexpected behavior requires investigation
4. **Planning needed** - The task is large, ambiguous, or has significant trade-offs to discuss
5. **You're stuck** - Multiple attempts without progress suggest a different approach is needed

## When NOT to Switch

Do NOT switch modes for:
- Simple, clear tasks that can be completed quickly in current mode
- Mid-implementation when you're making good progress
- Minor clarifying questions (just ask them)
- Tasks where the current mode is working well

## Available Modes
${n.join("\n")}

## Important Notes

- **Be proactive**: Don't wait for the user to ask you to switch modes
- **Explain briefly**: When switching, briefly explain why in your `explanation` parameter
- **Don't over-switch**: If the current mode is working, stay in it
- **User approval required**: Mode switches require user consent

Unexpected response for switch mode query: ${n.result.case}

User rejected the mode switch

Mode switched, updating state

Switched composer mode to ${t.toModeId}

Switched composer mode from ${t.fromModeId} to ${t.toModeId}

Error switching mode: ${e.result.value.error}

Mode switch was rejected by the user. Do not attempt to switch modes again.

Unknown error

Unhandled result case: ${e.result}

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

The description/content of the todo item

The current status of the todo item

Unique identifier for the todo item

Unique identifier for the TODO item

The description/content of the todo item

The current status of the TODO item

Unique identifier for the TODO item

The description/content of the TODO item

The current status of the TODO item

Whether to merge the todos with the existing todos. If true, the todos will be merged into the existing todos based on the id field. You can leave unchanged properties undefined. If false, the new todos will replace the existing todos.

Array of todo items to write to the workspace

Array of TODO items to update or create

Whether to merge the todos with the existing todos. If true, the todos will be merged into the existing todos based on the id field. You can leave unchanged properties undefined. If false, the new todos will replace the existing todos.

Array of TODO items to update or create

Whether to merge the todos with the existing todos. If true, the todos will be merged into the existing todos based on the id field. You can leave unchanged properties undefined. If false, the new todos will replace the existing todos.

Array of TODO items to update or create

Whether to merge the todos with the existing todos. If true, the todos will be merged into the existing todos based on the id field. You can leave unchanged properties undefined. If false, the new todos will replace the existing todos.

Unique identifier for the TODO item

The description/content of the TODO item

The current status of the TODO item

Unique identifier for the TODO item

The description/content of the TODO item

The current status of the TODO item

Array of TODO items to update

Array of TODO items to overwrite the existing TODO list with

Unhandled version: ${e}

Updates the todo list. Provide a list of todo items, each with an id, content, and status. Provide merge=true to update existing tasks.

### Guidelines
- At most one task can be in_progress at a time.
- Cancel tasks that are no longer needed immediately.
- Prefer creating the first todo as in_progress
- Batch todo updates with other tool calls in parallel

Use this tool to create and manage a structured task list for your current coding session.

Use this tool to create and manage a structured task list for your current coding session. This helps track progress, organize complex tasks, and demonstrate thoroughness.

Note: Other than when first creating todos, don't tell the user you're updating todos, just do it.

### When to Use This Tool

Use proactively for:
1. Complex multi-step tasks (3+ distinct steps)
2. Non-trivial tasks requiring careful planning
3. User explicitly requests todo list
4. User provides multiple tasks (numbered/comma-separated)
5. After receiving new instructions - capture requirements as todos (use merge=false to add new ones)
6. After completing tasks - mark complete with merge=true and add follow-ups
7. When starting new tasks - mark as in_progress (ideally only one at a time)

### When NOT to Use

Skip for:
1. Single, straightforward tasks
2. Trivial tasks with no organizational benefit
3. Tasks completable in < 3 trivial steps
4. Purely conversational/informational requests
5. Don't add a task to test the change unless asked, or you'll overfocus on testing

### Examples

<example>
  User: Add dark mode toggle to settings
  Assistant:
    - *Creates todo list:*
      1. Add state management [in_progress]
      2. Implement styles
      3. Create toggle component
      4. Update components
    - [Immediately begins working on todo 1 in the same tool call batch]
<reasoning>
  Multi-step feature with dependencies.
</reasoning>
</example>

<example>
  User: Rename getCwd to getCurrentWorkingDirectory across my project
  Assistant: *Searches codebase, finds 15 instances across 8 files*
  *Creates todo list with specific items for each file that needs updating*

<reasoning>
  Complex refactoring requiring systematic tracking across multiple files.
</reasoning>
</example>

<example>
  User: Implement user registration, product catalog, shopping cart, checkout flow.
  Assistant: *Creates todo list breaking down each feature into specific tasks*

<reasoning>
  Multiple complex features provided as list requiring organized task management.
</reasoning>
</example>

<example>
  User: Optimize my React app - it's rendering slowly.
  Assistant: *Analyzes codebase, identifies issues*
  *Creates todo list: 1) Memoization, 2) Virtualization, 3) Image optimization, 4) Fix state loops, 5) Code splitting*

<reasoning>
  Performance optimization requires multiple steps across different components.
</reasoning>
</example>

### Examples of When NOT to Use the Todo List

<example>
  User: What does git status do?
  Assistant: Shows current state of working directory and staging area...

<reasoning>
  Informational request with no coding task to complete.
</reasoning>
</example>

<example>
  User: Add comment to calculateTotal function.
  Assistant: *Uses edit tool to add comment*

<reasoning>
  Single straightforward task in one location.
</reasoning>
</example>

<example>
  User: Run npm install for me.
  Assistant: *Executes npm install* Command completed successfully...

<reasoning>
  Single command execution with immediate results.
</reasoning>
</example>

### Task States and Management

1. **Task States:**
  - pending: Not yet started
  - in_progress: Currently working on
  - completed: Finished successfully
  - cancelled: No longer needed

2. **Task Management:**
  - Update status in real-time
  - Mark complete IMMEDIATELY after finishing
  - Only ONE task in_progress at a time
  - Complete current tasks before starting new ones

3. **Task Breakdown:**
  - Create specific, actionable items
  - Break complex tasks into manageable steps
  - Use clear, descriptive names

4. **Parallel Todo Writes:**
  - Prefer creating the first todo as in_progress
  - Start working on todos by using tool calls in the same tool call batch as the todo write
  - Batch todo updates with other tool calls for better latency and lower costs for the user

When in doubt, use this tool. Proactive task management demonstrates attentiveness and ensures complete requirements.

Unhandled version: ${e}

Use this tool to manage complex multi-step tasks.

Invalid JSON

Invalid arguments: ${m.error.message}

Invalid argument: must provide 'content' for new todos items

Successfully updated TODOs. Make sure to follow and update your TODO list as you make progress. Cancel and add new TODO tasks as needed when the user makes a correction or follow-up request.

 No TODOs are marked in-progress, make sure to mark them before starting the next.

Here are the latest contents of your todo list:

${JSON.stringify(t)}

Here are the latest contents of your todo list:
${e.todos.map(e=>`- **${Xee(e.status).toUpperCase()}**: ${e.content} (id: ${e.id})`).join("\n")}

- **${Xee(e.status).toUpperCase()}**: ${e.content} (id: ${e.id})

You have many finished todos. Consider cleaning up old ones.

Unknown error

Unhandled result case: ${String(s)}

Object expected.