✋ Agent Sessions Tree is extremely inefficient

[benibenj]

• The agent sessions tree updates the entire tree far to often
  • Do not rerender the entire tree just to change the status label on one of the nodes. Have that single tree node update it's dom reactively based on the status changing
• The agent sessions tree updates even though it is not visible
  • Do not update the agent sessions tree if it is hidden/not visible. Update it when it becomes visible

These are all agent sessions tree update calls even though the tree is not visible

[bpasero]

I think the root cause is that the provider is not able to give me a good change event on a per-session basis, its just 1 event that something changed for the entire provider, so best I can do is to refresh the tree.

@mjbvz with your new API is there a way to get more fine grained events on a per-session basis?

[mjbvz]

Yes it does! This was actually one of the big motivations for move from a provider to a controller. I have already used this to optimize how much we send from the ext host to the main thread

However I haven't hooked this up fully on the main thread side yet. @bpasero How do you need this info exposed? I can pretty easily add two different events:

• An event that has just the diff of added and removed chat sessions

• An event that is fired when a property on an existing chat session is updated

[bpasero]

@mjbvz I think both would be great, I am not sure if the tree can efficiently update individual added and removed items, but we can build on top of that 🙏

Did we adopt your new API for CLI and Cloud sessions?

[benibenj]

I think this status message is causing a lot of tree updates:

Ideally we would not need to rerender the entire tree to change that label but instead the tree renderer would just listen on status change and rerender the dom node without telling the tree.

[DonJayamanne]

your new API for CLI and Cloud sessions?

I have started the work for CLI (unlikely I'll ship this in the next release/week), will be discussing the progress with @mjbvz separately