chatchan
Joined 3 months ago
Karma
75
Submissions
45
Member since
Jul 20
GNI Postdoctoral Fellow @TUM | Human-AI Alignment
View on Hacker NewsRecent submissions
Comment · 1 month ago
After releasing ThoughtDAG in August, the most significant feedback was that while editable context graphs were interesting, people didn't want to migrate their existing work to a separate application.
This prompted me to create Session Atlas. It reads local Codex and Claude Code sessions, organizes them by project, and retains conversations, tool calls, and results. The original session remains read-only, and the graph in ThoughtDAG is an editable mirror; content visible on the canvas doesn't automatically carry over to the next model request.
Now, you can select a context from a past session, launch a new CLI experiment, and then connect the results back to the original graph.
Currently, it's not bidirectionally synchronized, only supporting two local sources. But what I want to explore is: should Agent history be just a log, automatically remembered, or source material that can be reorganized and referenced by the user?
Previous HN discussion: https://news.ycombinator.com/item?id=49307700
Comment · 2 months ago
Thanks man! Any feedback is appreciated!
Comment · 2 months ago
Thanks for sharing, I agree with you. I also had the same struggle with bidirectional integration.
I think it makes a distinction here. Because I don't want to create "another" coding agent cli here. The core of my idea is to make context editable and flexible. It did help me when I do research to update information, condensate ideas, and prevent context pollution.
Comment · 2 months ago
Thanks, oh I see, Cypher acts as a context selector.
ThoughtDAG addresses the same issue but uses a visual approach: it searches for nodes first, then uses connections or references to determine which content enters the request. I'd love to see how it compares to writing Cypher directly, especially after conversations start branching and merging, if you get a chance to try it.
Comment · 2 months ago
Yes. I agree. I've added a small section to the README in the Git repository to describe how it works alongside your coding agent.
ThoughtDAG has automatic folder backups as a JSON file. So you can ask your CLI to access it and get the context in your harness tools :)
Comment · 2 months ago
Thank you for your feedback!
There is a way to delete a highlight. On the node side panel, there is a folded highlight section; you can manage your highlights there. Also, on your canvas, top-right ... menu, you can manage your highlights as well.
Comment · 2 months ago
Thanks! I'm not very familiar with Neo4j and Cypher yet. How do you control the context using Cypher? Do you manually write queries for each request, or do you select nodes through the interface and then automatically generate queries? I'm also curious about how the graph structure obtained from the query is ultimately transformed into an ordered model context.
Comment · 2 months ago
Thank you for sharing! That did occur to me. ThoughtDAG now marks affected downstream answers as needing updates after an upstream node is modified, allowing users to rerun the algorithm in dependency order; alternatively, automatic refresh can be enabled only for specific nodes.
I didn't rebuild the entire tree by default, mainly because modifying earlier nodes might trigger a large number of calls and could overwrite some still valuable intermediate results. Older answers are retained as historical versions for easy comparison.
Comment · 2 months ago
That sounds interesting. Could you share the arxiv papers? I would love to check them