A developer released semantic zoom in ThoughtDAG, an open-source conversation canvas supporting Ollama. Zooming out shows topics and takeaways; zooming in reveals summaries and full answers. The feature is a reading aid only — zoom level never changes what gets sent to the model.
ThoughtDAG is an open-source chat tool that lets users select a phrase in an LLM answer and explore it on a branch, then connect parts into the next question. It supports Ollama and OpenAI-compatible APIs, demonstrated with DeepSeek. It solves the problem of exploring tangents without disrupting the original conversation, for developers and researchers who chat with LLMs.
ThoughtDAG is an open-source chat tool that lets users select a phrase in an LLM answer and explore it on a branch, then connect parts into the next question. It supports Ollama and OpenAI-compatible APIs, demonstrated with DeepSeek. It solves the problem of exploring tangents without disrupting the original conversation, for developers and researchers who chat with LLMs.
ThoughtDAG is an open-source Ollama canvas that uses a directed acyclic graph (DAG) structure where each node is a question-answer exchange and edges determine the context sent to the LLM. When a user asks from a node, only its upstream ancestors are included in the prompt, making context explicit and editable. It solves the problem of linear chat interfaces that hide context, giving users fine-grained control over what the model sees.
ThoughtDAG is an open-source Ollama canvas that uses a directed acyclic graph (DAG) structure where each node is a question-answer exchange and edges determine the context sent to the LLM. When a user asks from a node, only its upstream ancestors are included in the prompt, making context explicit and editable. It solves the problem of linear chat interfaces that hide context, giving users fine-grained control over what the model sees.
ThoughtDAG is an open-source conversation canvas where you can branch AI discussions and wire chosen prior paths as context into the next answer. A history index finds candidate excerpts from past conversations, an optional step called Jev ranks relevance, and your regular LLM develops the answer. It targets people who work through research questions across sessions and want decisions carried forward without dragging entire old conversations along.
ThoughtDAG is an open-source conversation canvas where you can branch AI discussions and wire chosen prior paths as context into the next answer. A history index finds candidate excerpts from past conversations, an optional step called Jev ranks relevance, and your regular LLM develops the answer. It targets people who work through research questions across sessions and want decisions carried forward without dragging entire old conversations along.
ThoughtDAG is a tool that represents LLM conversation context as an editable directed acyclic graph (DAG), allowing users to visually manage and modify the context that influences the model's responses. It solves the problem of opaque and linear context in chat interfaces, giving users control over what the model sees. Aimed at developers and power users of LLMs.
ThoughtDAG is a tool that represents LLM conversation context as an editable directed acyclic graph (DAG), allowing users to visually manage and modify the context that influences the model's responses. It solves the problem of opaque and linear context in chat interfaces, giving users control over what the model sees. Aimed at developers and power users of LLMs.
ThoughtDAG is an experimental system that replaces automatic LLM memory retrieval with a visible, user-editable directed acyclic graph (DAG) of conversation nodes. Each question/answer exchange is a node, and edges determine which nodes are included in the next model request. Users can delete edges to remove branches from actual context, giving them direct control over what the LLM sees.
ThoughtDAG is an experimental system that replaces automatic LLM memory retrieval with a visible, user-editable directed acyclic graph (DAG) of conversation nodes. Each question/answer exchange is a node, and edges determine which nodes are included in the next model request. Users can delete edges to remove branches from actual context, giving them direct control over what the LLM sees.