How does it decide which elements to connect a new "thought" to? I'd imagine that can be quite complex if there's 300 elements on the map and you need to scan them all?! Or does the user do the job of arranging all the "thoughts"?

can you give an example of what a wire would be. like is it a human readable? LIke its literally a source?

Small update, especially for the earlier question about how a larger canvas chooses and follows connections: I have now released Session Atlas in v0.4.2.

It discovers supported local Codex and Claude Code sessions, groups them by project, and opens each session as a graph mirror. The source log stays read-only; the mirror is editable and can keep appending new turns while the source agent continues working.

The important boundary is that visible history is not automatically model context. Wires, explicit references, and attachment controls still determine what reaches the next request. So Atlas preserves the record without turning every imported turn into hidden memory.

45-second walkthrough: https://www.youtube.com/watch?v=Rs_KPYj2NCU

Guide and implementation details: https://chenxiachan.github.io/thoughtdag/docs/guides/session-atlas

I would still value criticism of the interaction cost: at what canvas size would you stop curating context manually and want automatic suggestions instead?