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?
chatchan•1h ago
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