Ask HN: Have you noticed an improvement in AI responses with memory disabled?
I decided I want to control this somehow, at least the procedure of how memories are collected, and where. Notes are captured when I ask, and periodically if agent feels that we have some "milestone" in conversation. This means I now can ask Claude to make the "handoff" from such jounrals (give the filesystem links of the needed journals + the additional information) to "onboard" the other agent.
- ▪I decided I want to control this somehow, at least the procedure of how memories are collected, and where.
- ▪Notes are captured when I ask, and periodically if agent feels that we have some "milestone" in conversation.
- ▪This means I now can ask Claude to make the "handoff" from such jounrals (give the filesystem links of the needed journals + the additional information) to "onboard" the other agent.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,336 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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 publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=49027099 |
| Publication time | Thu, 23 Jul 2026 19:49:47 +0000 |
| Retrieval time | 2026-07-23T20:11:52.789Z |
| Last seen | 2026-07-23T20:11:55.108Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | oI7Y6Zaucnek |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
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
It's same for me. I decided I want to control this somehow, at least the procedure of how memories are collected, and where. To be able to see them, process them, share them, mention them and outside of Claude storage, in my format.I work in Cowork with a filesystem I control, or in Claude Code and also with Codex.I instructed Claude and Codex to checkpoint into my external memory: keep a session journal in a fixed format markdown with front matter (date of creation, summary, keywords, status, links to related entries) and the body of such entry is the actual context and important notes, including also links to relevant files. (porbably what Claude or Codex could write in its own memories) and add such record to a common journal index.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.