Make it easier to open a workspace on hover
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
Currently, we hide most workspaces action buttons within the more actions dropdown, which is visible only on click after hovering on a workspace entry. Although the new workspace name (e.g. yellow-giraffe-c5e97000) is clickable and opens the workspace itself, it's not as discoverable at the moment.
| Workspace Name | Stopped Workspace |
|---|---|
![]() |
![]() |
Proposal
Similar to the more actions button, we can surface more actions on workspace hover to make it easier for the user to perform the most prominent actions like Open Workspace (see Proposal A).
| CURRENT (DEFAULT) | CURRENT (HOVER) | PROPOSAL A | PROPOSAL B |
|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
Other small specs:
- Action button can always read Open Workspace to match usage on stopped workspace page.
- The Last Active column can be hidden on hover to make room for the action buttons to surface.
- We can start by surfacing only the Open Workspace button.
- Proposal B shows how we could surface one more action for deleting workspaces or pinning workspaces.
See also relevant specs, in case these can help.
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
Start by locating the workspace list UI and reviewing the linked Figma spec, especially Proposal A and Proposal B. Confirm which hover behavior is intended, then make the Open Workspace action discoverable on hover while checking the Last Active column and existing workspace actions. Done means the chosen design works for active and stopped workspaces and matches the stated button wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100





