Originally created by @TheElo on GitHub (Feb 7, 2025).
Feature Request
Important Notes
Note: Please remove the notes above when submitting your post. Thank you for your understanding and support!
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
The chat overview becomes very confusing and convuluted in even slightly more complex conversations. The issues are:
AB -> second conversation moves in the lane of the first one, the lower nodes are not related, they shouldn't be close to each other
CD -> unclear arrow pointing, due to arrows and edges to close to each other at corners, hard to see the line of conversation/choices
EF -> the more conversations you add the more confusing it gets due to increased distance of related nodes and position variation due to previos nodes positions
Describe the solution you'd like
Basically columns, so each split has it's own line. No crossing of lanes/columns. Split are centered below the previos node.
this way it's visually clear and easy to track the conversation
Describe alternatives you've considered
I'm not aware of alternatives.
Additional context
Add any other context or screenshots about the feature request here.
Originally created by @TheElo on GitHub (Feb 7, 2025).
# Feature Request
## Important Notes
Note: Please remove the notes above when submitting your post. Thank you for your understanding and support!
---
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
The chat overview becomes very confusing and convuluted in even slightly more complex conversations. The issues are:

AB -> second conversation moves in the lane of the first one, the lower nodes are not related, they shouldn't be close to each other
CD -> unclear arrow pointing, due to arrows and edges to close to each other at corners, hard to see the line of conversation/choices
EF -> the more conversations you add the more confusing it gets due to increased distance of related nodes and position variation due to previos nodes positions
**Describe the solution you'd like**
Basically columns, so each split has it's own line. No crossing of lanes/columns. Split are centered below the previos node.

this way it's visually clear and easy to track the conversation
**Describe alternatives you've considered**
I'm not aware of alternatives.
**Additional context**
Add any other context or screenshots about the feature request here.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @TheElo on GitHub (Feb 7, 2025).
Feature Request
Important Notes
Note: Please remove the notes above when submitting your post. Thank you for your understanding and support!
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
The chat overview becomes very confusing and convuluted in even slightly more complex conversations. The issues are:
AB -> second conversation moves in the lane of the first one, the lower nodes are not related, they shouldn't be close to each other
CD -> unclear arrow pointing, due to arrows and edges to close to each other at corners, hard to see the line of conversation/choices
EF -> the more conversations you add the more confusing it gets due to increased distance of related nodes and position variation due to previos nodes positions
Describe the solution you'd like
Basically columns, so each split has it's own line. No crossing of lanes/columns. Split are centered below the previos node.
this way it's visually clear and easy to track the conversation
Describe alternatives you've considered
I'm not aware of alternatives.
Additional context
Add any other context or screenshots about the feature request here.
@TheElo commented on GitHub (Feb 7, 2025):
real life example