Allow autogenerated names back into in the workspace URL
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe
Context:
This pertains to a typical workflow where the user is running multiple instances of the same workspace. I do this often when testing out and comparing gitpod configurations.
The Problem:
Now that the autogenerated name (i.e.
harlequin-crayfish) in the workspace URL has been replaced with the repository name there is no real good way to identify multiple versions of the same workspace running in gitpod.
Two workspace urls open side by side will look something like this:
https://gitpodio-apacheexample-xpbkletuqfe.ws-us27.gitpod.io/
https://gitpodio-apacheexample-tmbletixgk.ws-us27.gitpod.io/
To make things even harder, now that the repo name is in the first part of the workspace URL two tabs in the browser can look exactly the same:

Describe the behaviour you'd like
There are Many ways to handle this. One flexible solution would be to have a setting in the dashboard that allows the user to toggle the ability to prefix the workspace url (as it was before) with a somewhat unique human readable autogenerated name (i.e.
harlequin-crayfish) either in addition to the repository name or replacing it.
Describe alternatives you've considered
I can't think of any workarounds since the generation of the workspace URL is not exposed to the user.
Additional context
Putting the repository name in the workspace url is generally helpful and I cant totally see why this was done but it does affect the workflow where a user runs mulitple versions of the same workspace in that if becomes almost impossible to distinguish them at a glance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; first locate the workspace URL generation path and clarify whether the repository name, autogenerated name, or both should be configurable. Done means multiple instances of the same workspace are distinguishable at a glance while preserving the useful repository name.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100