Repository navigation
Search and reopen archived workspaces from the command center (⌘K) #6345
Replies: 2 comments
|
After reading CONTRIBUTING.md, I see two reasonable ways to close this gap, and I'd be glad to help with whichever fits Paseo better. Option A: native support in ⌘K. Archived workspaces show up in command center results, below active ones or in their own section, and selecting one restores the workspace and unarchives its agent without starting a turn. This gives everyone the workflow out of the box and makes archiving feel safe by default, with no plugin to install. Option B: extension points in the plugin API. Today a plugin can't list archived workspaces ( Either one solves my use case. I'm willing to contribute the implementation for whichever you prefer, but given the guidance in CONTRIBUTING.md I'll wait for a signal that one of them is wanted, and in what shape, before writing any code. |
|
Cmd+K now finds archived workspaces in core, from #9689. When you type a search, matching archived workspaces are listed after the active ones with an Archived badge, and picking one opens its archived screen, where Unarchive restores it. It isn't in a release yet. It will be in the next beta and then stable, and Updates explains how to join the beta. This change doesn't add plugin API for listing or restoring archived workspaces. |
Uh oh!
There was an error while loading. Please reload this page.
Archiving is the natural way to keep the sidebar focused on what I'm actively working on, but today it also hides the workspace from ⌘K. Getting it back means going to History and restoring it by hand, so archiving feels riskier than it should and I end up leaving finished workspaces in the sidebar instead.
Proposal: include archived workspaces in ⌘K results, ranked below active ones or in their own section, and restore the workspace and unarchive its agent when one is selected, without starting a turn.
I built this as a plugin to scratch my own itch: saratscheff/paseo-reopen-archived. It works, but it has to read the daemon registry files and send internal restore and unarchive requests, because the plugin API can't list archived workspaces or restore them. That makes it fragile across releases, and I think this belongs in core rather than in a plugin.
Related: #6037 (filtering History by archived state).
All reactions