Rule-based chat naming conventions (agent-driven, configurable titles)

Ideas Feature Requests
,
1

Feature request for product/service

Chat

Describe the request

PROBLEM

Chat titles are auto-generated from conversation content, and the only way to
impose a naming convention is to manually rename each chat (right-click →
Rename, or /rename in the CLI). There’s no way to:

  • Enforce a consistent title format across a team or project
  • Include structured metadata in the title (mode, scope, branch, ticket ID, etc.)
  • Have the agent name the chat itself based on instructions

For anyone who organizes work by convention – e.g. Conventional Commits, “ask | chat naming
conventions”, “feat(api) referral webhook”, “bug#1234 draft save parity” –
every title has to be typed by hand, and the auto-generated titles omit useful
signal like the chat mode.

REQUEST

Let chat naming be driven by a configurable rule, similar to how .cursor/rules
and AGENTS.md already steer agent behavior. Ideally:

  1. A title template / pattern definable at the user or project level, e.g. <mode / intent> | <topic>, with tokens the agent fills in.
  2. Agent-fillable slots so the model populates / from the conversation while the fixed structure stays consistent.

WHY IT HELPS

  • Consistent, scannable chat lists across a team
  • Encodes convention once instead of re-typing every title
  • Fits Cursor’s existing rule-based configuration model, so it’s discoverable
    and version-controllable

NICE-TO-HAVES

  • Per-project override of a global default template
  • Tokens for mode, git branch, and active model
  • Optional lock so auto-generation doesn’t overwrite a rule-formatted title

Operating System (if it applies)

MacOS

5

Hi @MishaTheMisha, Thanks for the post! This is known ask we are tracking internally, and I’ve added your post to the existing feature request.