When a new Brain AI conversation is initiated from (or tagged to) a specific task, the conversation title should automatically adopt a naming convention that includes the task name or key identifiers from it (e.g. custom task name).
Problem:
When running multiple Brain conversations across multiple tasks, especially in batch workflows, the auto-generated titles end up nearly identical ("Status Update and Next Ste…", "Proposal Status and Next Ste…", etc.). Scrolling through the conversation list becomes a guessing game since there's no way to tell which conversation belongs to which task without clicking into each one.
Expected behaviour:
If a conversation is linked to a task, prefix or incorporate the task name into the conversation title. For example:
"[Website Errors] Status Update and Next Steps"
"[Website Migration] Status Update & Next Steps"
Why it matters:
Project workflows that often involve running the same type of prompt across dozens of client tasks in a single session. Without clear naming, context-switching between conversations burns time and increases the risk of applying the wrong output to the wrong task.
Attached is an example of the pain point.

Photo Viewer

View photos in a modal