Dylan explains why the old advice to "start fresh chats often" has partly changed: compaction (auto-summarizing long chats) and native memory in Claude and ChatGPT now make long conversations viable, but mainly in desktop agents like Claude Cowork and Codex rather than in the browser. He lays out two setups: Setup A, fresh chats in a task-dedicated folder with an instructions file (claude.md / agents.md) plus an externalized memory file, which covers ~95% of use cases; and Setup B, a pinned thread that runs for weeks or months, only for tasks with no finish line where yesterday's context helps today's work (inbox assistant, long-running project monitoring). Both setups rely on keeping memory files short (150-200 lines), pruning them periodically with approval, and, for pinned threads, generating a one-to-two-page handoff document when intelligence degrades and it's time to start a new thread.
- Two recent improvements enable longer chats: compaction, where the AI silently summarizes earlier conversation to itself, and native memory, which still only stores surface-level facts like name, location, job, and broad preferences.
- The benefits are unevenly distributed — in the browser you won't see much gain; compaction and memory work much better in desktop agents (Claude Cowork for Claude, Codex for ChatGPT), which are included with existing subscriptions.
- Setup A (recommended for ~95% of work): a folder per finite task with an instructions file that defines the purpose, points to a memory file, and tells the AI to append short dated lines whenever it's corrected — giving both fresh-chat intelligence and accumulated preferences.
- Setup B (pinned long thread) only passes two tests: the task has no finish line, and today's work benefits from knowing what happened yesterday. If you're hesitant, default to Setup A.
- Best Setup B use cases are an inbox assistant that triages, researches, and drafts replies (the one Dylan says OpenAI people discuss most) and monitoring a 6-12 month project with recurring updates.
- Don't build a thread around a client — a client is a topic, not a task. Use a parent client folder with subfolders for each task (proposals, contracts, questions).
- Even a well-run pinned thread eventually degrades — the AI forgets obvious facts and contradicts itself. Ask it for a one-to-two-page handoff document, then start a new chat in the same folder so the memory and loops files carry over.
- Memory files must stay dense and under roughly 150-200 lines; run a weekly or monthly audit where the AI flags stale, repeated, or untrue lines, moves them to an archive folder rather than deleting, and shows you changes for approval before acting.
This is the decision rule the whole video hinges on, stated compactly enough to act on immediately.
Is there a finish line? If there isn't a finish line, it might be good for this setup B. Second question, is it beneficial to understand what happened yesterday in the thread for today's work?
It names the most common structuring mistake and gives the concrete parent-folder/subfolder fix.
"Oh, I have this huge client that I want to have an ongoing thread for." That's a bad idea because for a given client, that's a topic not a task.
Its intelligence dropped like a rock after around 50% of filling up its head.
For a given client, that's a topic not a task.
Every lesson worth keeping starts as the decision your AI made without you asking.