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
{{ message }}
Repository navigation
tasks: name the workspace/task based on a summary #18159
Today, the task shows up as the full prompt and the workspace is a random name.
I suggest we name the workspace based on an AI summary of what the task is working on. For example in this case, the workspace could be named: nexus-cleanup
Coder already imports aisdk-go, so we could use a lightweight model to name the workspace.
I suppose we'll need to AI-generate both the task name and the workspace slug, with automatically generated fallbacks in case the LLM API isn't responding or the admin hasn't configured one.
For fallbacks, I suggest using something like ai-lime-duck-32 for the slug and the first 32 characters of the prompt for the name.
Activity
hugodutka commentedon Jun 6, 2025
I suppose we'll need to AI-generate both the task name and the workspace slug, with automatically generated fallbacks in case the LLM API isn't responding or the admin hasn't configured one.
For fallbacks, I suggest using something like
ai-lime-duck-32for the slug and the first 32 characters of the prompt for the name.feat(coderd): generate task names based on their prompt (#19335)