Here's some recent frontend work that includes many UX papercuts in the product. I'll be pushing a lot more for feedback. I will also have the branch ready with PRs broken out for inspection. I'll also be highlighting some "in progress" pages with some improvements to how people set up a factory

Looking nice! I wonder if it’d make sense to put “documentation, slack, github” in the top right? That seems to be a popular place for those types of buttons

So I added to the dashboard a new system of positioning items. User can turn them on or off and move their position. Hypothetically we can allow the user to stick it anywhere. 🙂 Currently, you can remove it with a X I put on all components that turns them off.

I’d LOVE to get PR status icons on the conversations! Could you add any visuals you have in mind to this issue if you get a chance Paul github.com/OpenHands/OpenHands/issues/19030

Yeah, I have the subagent view too, it just needs cleaning up:

looks like git changes too

those are the change diffs, yeah

Awesome look! Re: merged 🤔 we're assuming there’s a single PR per conversation?

@calm-artist-7206 assuming last status or current status of open work in the session

Whatever Claude, codex, copilot, t3 and others do. Everyone seems to have PR icon

I see where you’re coming from, it would be useful to show it’s dirty… what if theres a merged PR and then it’s dirty again? I use my ipad a lot, and it doesn’t have these in codex/cc In this image, these go further and I’m just musing, thinking it’s better for moving up, for doing more with agents than the user can do in short disconnected chats. On codex or idk where, there’s a pill just above the composer, with number of PRs from that thread

Dirty Branch Uncommited Work Idle Committing Pushing/Merging Conflict Block Merge Complete Branching Creating New Worktree Creating New Subagent

Here is my thinking, please poke holes in it: We have seen quite a lot of users who came and asked “why doesn’t OpenHands allow multiple repositories?” But it does! The agent can do it. Just have it clone more repositories. I note that it did, since ~forever, while major labs’ agents and other agents were indeed stuck to one repo, e.g. Anthropic’s cloud was terrible on this. Same for long running conversations, which have maybe one repo, but many PRs. Somehow, the UI seems to tell people that they can’t do it. So what can we do? Two possibilities: • have some hint, or UI element(s), or rethink the UI, for people to use multiple repos • not suggest in other UI elements that it’s limited. The second point is what I’m wondering about, here: a conversation can be long, can have multiple repos so multiple PRs, multiple subagents so multiple PRs, etc etc. If we show “the” PR status, does it suggest a bit that it’s a PR per conversation? Or close to it? Like, you can do a second PR, but probably doesn’t help you imagine you could do much more. Maybe we could use other parts of the UI for showing the PR status? I don't know. Maybe it’s nothing, or too little to matter. Anyway, attached is Codex iPad app, it’s a pill on the conversation view. It’s a bit funny! It stopped counting at 100 😅. Though I continued with more subagents, each with their PR.

What if the status itself was clickable and shows a status of all work and their merge status AND it shows the most recent change as the main icon.

The conversation status in the left panel... what if we simplify? Q: "What needs user's attention?" A: "In these conversations, things happened, the agent finished its turn and responded, but they never read the agent's response"