WeSearch

I built a canvas where LLM chats become an editable map

·2 min read · 0 reactions · 0 comments · 12 views
I built a canvas where LLM chats become an editable map
TL;DR · WeSearch summary

An infinite canvas where LLM conversations grow into an editable thought graph. ▶ Try it live no install, no signup; the example canvas needs no key 中文 · Quick start · More capabilities · Models · Cost & privacy The one rule Wires are the context. What the model sees is exactly what wires into the node. In action One principle behind every gesture: the human in the loop, the model on the wires.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 3,306 of its stories.

Original article
GitHub
Read full at GitHub →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherGitHub
Canonical URLhttps://github.com/chenxiachan/thoughtdag
Publication timeSun, 26 Jul 2026 11:42:22 +0000
Retrieval time2026-07-26T11:58:02.358Z
Last seen2026-07-26T11:58:02.358Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterS3s3Gp1K2GZF
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

ThoughtDAG Your thinking deserves a map. An infinite canvas where LLM conversations grow into an editable thought graph. ▶ Try it live no install, no signup; the example canvas needs no key 中文 · Quick start · More capabilities · Models · Cost & privacy The one rule Wires are the context. What the model sees is exactly what wires into the node. Editing the graph edits the model's memory. In action One principle behind every gesture: the human in the loop, the model on the wires. No autonomous agent redraws your graph. ✂️ Delete one edge, get a different answer The model sees only what wires in. Delete the noise edge, ask again, and the same prompt returns a clean answer. Reproduce it in chapter ③ of the example canvas. 📖 Read a paper into a map Select a passage, ask right there.

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub