Long Sessions Within An Agent Node

Hello, I've got a coaching agent that guides the user through several question sets and frameworks. Only thing I've realized is a lot of the conversation is spent inside of a single agent node, which inevitably leads to pegging out max tokens inside of the single node.

When this happens, the user gets no notification and their queries seem to fall on deaf ears as the agent just stops responding completely (even though I can see tokens still getting consumed on the backend logs).

Wondering if any of you have dealt with this in a sophisticated way.

Thanks,

-Conner