Task context by branch ( maybe a .cursortask file?)

Overview:

Currently, when starting a new task, I include the objective of the task in the .cursorrules file. This helps keep the task context readily available during development.

Example Use Case:

Imagine a scenario where a Jira ticket requires implementing a new API integration with a third-party service triggered when a new user is added.

With .cursorrules, I can add the task context, such as the title, description, and other relevant details, directly into the file. This way, I don’t have to repeatedly reference Jira or other documentation while interacting with the codebase.

Proposed Feature:

It would be incredibly useful if Cursor’s LLM could:

  1. Automatically leverage the task context from .cursorrules to provide contextually aware suggestions and answers.
  2. Dynamically update the task context when switching branches. For example, when moving from one feature branch to another, the task context could seamlessly change to reflect the objectives of the current branch.

Benefits:

  • Improved productivity by reducing context-switching between tools and documentation.
  • More accurate and relevant suggestions from the LLM based on the current task.
  • Enhanced collaboration, as the .cursorrules file becomes a shared source of truth for the task context across branches.

I believe this feature would greatly enhance the development experience for teams using Cursor, especially for tasks that span multiple branches.