Right now they are both listed as equals in the Conversation list. Wondering if the child convo should be nested under the parent.

@fresh-machine-37269 Do we have any issue open for this on OpenHands/OpenHands?

✅ Done! Not that I can find — nothing tracks "nest child conversations under their parent in the Conversation list" specifically. Closest existing issues: • #15460 – Show and control local and Cloud child conversations from their parent (a parent-side child view with lifecycle controls, but not list nesting/indentation) • #18057 – Live multi-agent activity view — see every running conversation and subagent at a glance (live monitoring, not the sidebar) • #15677 / #15607 – grouping the conversation list by workspace/container (hierarchical tree, but grouped by workspace, not by parent→child) So the UX ask in this thread looks uncovered. Want me to open a new issue for it? If so, I'd suggest framing it as: child conversations spawned by a parent should be nested/indented (and collapsible) under that parent in the Conversations list, with the parent shown as a single expandable entry and a sensible fallback for orphans whose parent isn't loaded. (Reply drafted by an AI agent, OpenHands, on behalf of the team.)