I wanted to organize things and couldn't figure out how to add a workspace thru the UI. It looks like there are already 3 issues already related to this pinch: > - #15775 (DevinVinson, 05-28) : "I need to click Open Workspace in conversation view, then click the dropdown, then click manage. That same number of steps needs to happen to add a new workspace." It even quotes a user hitting the "Add all subdirectories" trap. > - #15974 (xingyaoww, 05-13, 7 comments) covers the workspace/worktree confusion. > - #16435 (rbren, 08-08) is about grouping-by-workspace needing all workspaces visible. Is this already being handled internally or would a prototype be helpful?

I've got some wireframes and prototypes floating around but I'd love to see what you have in mind!

Yeah, I wanted to create a new workspace. I didn't want to read old convos and determine value so I wanted to make a trash folder and put all of my existing conversations in it. Anything that stays in there long enough will eventually get reaped. I've not gone deep yet but it seems like 'selected_workspace' is written once and there's nothing that changes it yet. So, in my imagination, I'd build a prototype that covers my use case after assimilating those 3 issues. The impact it has on the UI would be incidental. Probably 2 new buttons? 'New Directory' on the first and 'Move Conversation' on the second?

Sounds like a plan! If you have not stumbled into it before check out the conversation Filters and scroll all the way to the bottom. There is a toggle to hide old conversations and then a Delete all button. Just pointing those out in case it helps with part of what you are looking for

@hundreds-twilight-32833 Here's how I think it will look like:

1. PR 1 — agent-canvas: Move Conversation. Self-contained, client-side, zero cross-repo dependency. The mutable org key in the metadata store follows the established upstream pattern (active_profile is client-side there for the same reason), grouping reads organized_workspace ?? selected_workspace. This PR is the diagnosis in diff form, and it's the fastest thing to get merge-ready — which matters given the supersession rate.

2. PR 2 — software-agent-sdk: create_directory route in file_router.py + FileClient method (need to verify whether typescript-client is generated from that repo — planning detail).

3. PR 3 — agent-canvas: New Directory in the folder browser, consuming PR 2.

Yep, make sure there isn't some unknown issue with creating a directory via agent-server.

Sorry I’m dense, do you want to create • a directory where the conversation events/logs/data are saved, or • a directory where a repo or more exist, where the agent works?

That's an interesting question. I opened it up and my first instinct was to clear the noise. Reflexively, looking at the UI, I want to drag these old conversations into a folder. So I click on the new folder icon and that gives me Workspaces. I add the workspace but at this dialog, I have to already have a directory created. Easy peasy if I understand what I'm looking at and can just mkdir. But if I can do is 'Add all subdirectories' that's a big problem if I don't know how to get a subdirectory in there.

Cool, I don’t think it will hide the long list of conversations, that’s all: in the image below “where are you?” is in a new directory=workspace, but you see how it displays the same

Yes, I think you are right. I've been down this road before and I would advocate for tagging, especially with the idea of themes on the map. Let users tag conversations with anything our little hearts desire. They can be tagged as folders, projects, slightly expired fruit, the sky is the limit! Nesting becomes a function of labels instead of a footgun.

Oh, I see! Thank you for the review on 16444!

yeah, you're right. tagging isn't really properly exposed in the ui, tho. i'm working on a prototype so we have something to look at. doing server-side filtering of tags looks like it would need another endpoint so i'll do mvp clientside

It is definitely getting a bit full but I'm not sure about that little Filter chip

yeah, the hamburger menu became scrollable when tags were in there

Maybe a modal for sidebar UI options is needed. Give it some room, add some easy presets like compact, minimal, detailed

yeah, that makes sense

Filter gives you some basic options then a expanded modal view gives you all of them?

but that's clearly a much bigger convo so i dialed back lol

I have some ideas here if you want to push that branch of as a draft

will do

I've been playing around with this a bit @straight-dog-12443. What is your main use-case for adding custom tags and then being able to filter by tags? Any specific user story in mind?

Nothing specific. It's just a mutation of my reflex to declutter the screen somehow. I recall somebody mentioning themes or skins or something along those lines as being the future of the product. Tags are a flexible way to do customizable nested organization because then the user/theme can define structure. Tags were already present in the SDK but before we could consider using them for visual organization, we would need for them to be present on the UI somehow. Tags without filtering didn't make sense to me. If anything, I think it's more likely that the tag filter/search will be moved to the server by adding an SDK endpoint later. The browser-based filtering just offers an MVP without requiring the SDK PR as well.

Ah gotcha. Tags right now get added for automation runs but it doesn't seem to be all the time and I'm not sure under what context they are added for any other purpose. I'm not in love with this flow but its an idea of a direction

ui tags are isolated from automation tags - Advanced options->Tag chips

That looks really slick @straight-dog-12443! Do you want to move it out of draft and we can pull in @breezy-kilobyte-39430 to help give some additional design reivew?

I'm not in love with this flow but its an idea of a direction

It does seem too much to click, and there are two things far from each other, that go together... 🤔 At a minimum, maybe we could have only an "enable tags"? That would both show and allow filtering

Thats a good idea! I think a slow setting by setting and flow by flow run through will help challenge the changes too. I originally thought the different layout options should disabled the 1 hour recent convo toggle but going through it makes it a bit confusing if you have not had a conversation recently. But overall the simplification feels good to just click a layout style with one click. Hoping we get some more eyes on it once its out of draft state too. I would guess few people have looked at all the filter options or know they exist tbh

i'm working on switching over to that branch and making the issue so i can mark it ready for review

is an SDK endpoint necessary? do we know what the specification of missing tag operations is?

for tags? an endpoint was not necessary unless there's a need for server-side features, i think

I'm just wondering if we should persist them. Tags exist in the SDK since this PR: github.com/OpenHands/software-agent-sdk/pull/2454

yeah, that's what it uses

Cool!

out of draft but CI won't be happy until the issue says ready-for-dev. i'm not sure how far out of draft you want it @hundreds-twilight-32833 github.com/OpenHands/OpenHands/pull/16600

Please don't worry about that, it shouldn't matter; the label is merely in an attempt to stem the tide of AI PRs that humans didn't think through, as you may know - it's not our case here 😅