I've been playing with nested sessions and I see that, of course, the parent ...

I've been playing with nested sessions and I see that, of course, the parent can see the child and viceversa, but noticed that really any session can see any other open session. So two things
1. Sometimes I may have ton of sessions and I don't want a session "tree" from being able to see another stree (or it might get confusing for that agent). Similarly, it would be great to control if sessions can see their siblings or just parent/child. A setting to control how this discovery behavior works would be awesome
2. Sometimes I've wanted a session tree to be reparented under another. Right now this forks in practice because any session can see any other so I can just tell "root A" to take charge of "root B". But this change is not really reflected in the UI. It would be cool if we could move a "tree" from one place to another

---
| Field | Value |
| --- | --- |
| App version | 1.1.0 |
| OS | Windows 10.0.26200 |
| Theme | Fox |
| Path | /chat |
| Tenure | Week 3 |

Empieza en la ruta /chat y reproduce el comportamiento de sesiones anidadas descrito en el issue, incluida la visibilidad entre sesiones no relacionadas y la UI actual después de que una sesión tome el control de otra. Se considera terminado cuando el comportamiento de descubrimiento se puede controlar para árboles separados y para la visibilidad entre padres e hijos o entre sesiones hermanas, y cuando mover un árbol de sesiones se refleja en la UI.

Escrito por el modelo de indexación a partir del texto del issue.