You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tasks are basically fancy Workspaces that can do AI stuff. We can name & rename a Workspace (if enabled in your template). Tasks can't be renamed. Let's be consistent about the capabilities!
Our Current UI:
Proposed UI:
The Ask
Need to work with UI/UX, but be able to name a Task at creation
Let's add the meatball menu at the end of a individual Task, and list there the ability to rename the Task. We don't need the other UI modifications
Suggestion: for rename, add an editable "display name".
This can then be the target of the current "automatic naming" functionality:
Initially tasks are created with a non-AI-generated name
They then have a "display name" generated async in the background
This is what a lot of existing providers do.
Note that we only currently support Anthropic API keys for this. Maybe this could be done in the UI directly somehow?
After internal discussion, it was decided not to move forward with the task name/rename flow for now. This decision was mainly because there are already design mockups that include these flows and would require additional frontend work to implement. Making these changes now would likely lead to rework once the new mockups are applied.
The current focus will be on ensuring task naming readability and consistency across views. As part of this, we’ll introduce a new Display Name, as suggested in #20226 (comment). This work will be tracked under #20455.
Renaming the display name would be extremely valuable, especially in cases where the AI summary gets it wrong, or a GH issue URL is read by an agent and the agent wants to name it based on what the actual issue description says
Activity
[-]feat: add ability to rename task[/-][+]feat: add ability to name & rename task[/+]johnstcn commentedon Oct 22, 2025
@david-fraley Where should the option to name a task appear on the creation page?
Should we start off with CLI renaming support first?
johnstcn commentedon Oct 22, 2025
Suggestion: for rename, add an editable "display name".
This can then be the target of the current "automatic naming" functionality:
This is what a lot of existing providers do.
Note that we only currently support Anthropic API keys for this. Maybe this could be done in the UI directly somehow?
ssncferreira commentedon Nov 13, 2025
After internal discussion, it was decided not to move forward with the task name/rename flow for now. This decision was mainly because there are already design mockups that include these flows and would require additional frontend work to implement. Making these changes now would likely lead to rework once the new mockups are applied.
The current focus will be on ensuring task naming readability and consistency across views. As part of this, we’ll introduce a new Display Name, as suggested in #20226 (comment). This work will be tracked under #20455.
More context is available in the internal Slack thread and meeting notes.
bpmct commentedon Dec 7, 2025
Renaming the display name would be extremely valuable, especially in cases where the AI summary gets it wrong, or a GH issue URL is read by an agent and the agent wants to name it based on what the actual issue description says
matifali commentedon Sep 13, 2026
Tasks are deprecated in Coder version 2.34 and above. Please follow https://coder.com/docs/v2.37/ai-coder/agents/tasks-to-chats-migration for a migration path.