An old assumption keeps coming back.
Inspect the next request. Remove an unwanted route, keep the earlier discussion, and regenerate.
How to edit AI context →ThoughtDAG · Open source · MIT
ThoughtDAG is an open-source AI conversation canvas. Edit the context sent to your model, explore a side question, and bring selected past discussions into what you ask next.
Inspect the next request. Remove an unwanted route, keep the earlier discussion, and regenerate.
How to edit AI context →Explore a branch, keep your place in the map, and connect useful findings to a later question.
How to branch an AI conversation →Find supported local conversations, check the original conditions, and cite the parts you need.
How to reuse past AI discussions →Illustrated workflows. Each tutorial includes steps to try in the app and a downloadable GIF.
Yes. Removing a wire removes that route into a later request while keeping the nodes. Check other input paths, attachments, and Recall too. An existing answer does not change until you edit or regenerate it.
Keep alternative questions on separate branches, compare them on the canvas, and connect selected findings to a new downstream question. A branch inherits its upstream conversation path; selecting a passage does not limit context to those words alone.
No. The desktop app indexes supported local records you have connected. It cannot restore unsaved history or automatically access chats stored only in a web account. When you use a remote model, the material included in a request is sent to that service.
ThoughtDAG
Scroll
The history is here. Which parts enter the next request?
This history should not enter the research summary.
Still connectedThe prompt stayed the same. Polluted context changed the answer.
Includes unrelated branchIncoming ancestors:
Research question Evidence A Dinner detourAfter deleting the orange edge: −47 tokens
The words are identical. Only one edge changed.
Reproducible contextThe unrelated dinner suggestion is gone.
Answer updated in placeNo hidden memory selector. What the model sees, why, and what was removed stay visible in the graph.
Visible Editable InspectableThe interface shows what was said, not which history enters the next request.
Ask from a selected passage, or turn a passage or figure into its own source-linked node. Provenance stays attached; context remains yours to wire.
Preview source nodes, order, and token count. Context is no longer a hidden decision.
The removed branch really leaves the request. The answer changes with the context.
You decide what enters and leaves. The graph is the context protocol before generation.
ThoughtDAG walks the incoming edges of a node, orders the relevant ancestors, and builds the message sequence sent to the selected model. The structure stays visible, editable, and inspectable.
Explore another interpretation without overwriting the path that led you here.
Keep a useful detour on the canvas while excluding it from the next request.
Bring selected evidence and reasoning paths back together in one answer.
Preview what the model will receive before generation. No hidden memory selection.
Search with your agent, work inside Harness, or open the standalone app. Choose one to start.
Search conversations across supported agents and let your agent call the query tools directly. The desktop app is not required.
CLI and MCP manual →npm install -g thoughtdag
thoughtdag setup mcp
Add the thought graph to the web UI. Use your harness models, run agent turns, and explore sessions in Atlas. No separate ThoughtDAG app or CLI required.
Installation and usage → Plugin file on every release (.tgz): the same command takes its URL →dsh plugin --profile web add dsh-thoughtdag
dsh web
The same app in its own window, local engine bundled. No Node, no terminal.
v0.5.19brew install --cask thoughtdag
All versions and history live on GitHub Releases.