I built oMyTree because I kept getting lost in long AI chats.
Once a conversation grew past 20–30 messages, I couldn’t track how ideas branched or why a certain line of reasoning started. Scrolling felt like the wrong interface for thinking.
So I tried a different approach: treat a conversation as a tree — each message becomes a node, and each follow-up grows a branch. It’s not a “knowledge tree” or a curated outline; it’s just a visual map of the raw conversation, exactly as it happened, but structured in a way that’s easier to explore.
I’d really love feedback from the HN crowd on:
– Whether this UI pattern reduces cognitive load
– Where it breaks down for complex threads
– What workflows it might actually help (learning, research, debugging, etc.)
– Whether anyone has tried similar interaction models before
Happy to answer anything about the design, tradeoffs, or the tech behind it.
isbeingto•1h ago
I built oMyTree because I kept getting lost in long AI chats. Once a conversation grew past 20–30 messages, I couldn’t track how ideas branched or why a certain line of reasoning started. Scrolling felt like the wrong interface for thinking.
So I tried a different approach: treat a conversation as a tree — each message becomes a node, and each follow-up grows a branch. It’s not a “knowledge tree” or a curated outline; it’s just a visual map of the raw conversation, exactly as it happened, but structured in a way that’s easier to explore.
I’d really love feedback from the HN crowd on:
– Whether this UI pattern reduces cognitive load – Where it breaks down for complex threads – What workflows it might actually help (learning, research, debugging, etc.) – Whether anyone has tried similar interaction models before
Happy to answer anything about the design, tradeoffs, or the tech behind it.