File it at creation, then write the short version
Build-along · ~10 min at your own keyboard
Every workspace acquires an inbox, and every inbox becomes a graveyard, because outputs arrive faster than anyone sorts them. The fix is to decide where a thing lives before you make it, so filing is a side effect of the work rather than a chore that comes after. The second half is what makes the folder compound: at the end of a session, write down what got decided and what changed — short — and file that. Next time you load the page, not the transcript. A workspace that stores everything raw gets slower every month; one that stores distillate gets more useful. And once the folder holds the memory, closing the chat costs you nothing, which is the actual payoff.
The long version: Filing at creation ↗
Do this
0/5Checkpoints
- ▸You should now see a named home folder for the output before you start.
- ▸You should now see the file landing in that folder as it is created.
- ▸You should now see a session note well under a page.
- ▸You should now see a cold session answer three continuation questions from the note alone.
The three ways this goes wrong
- The output ends up in Downloads or on the Desktop. — Say the full folder path in the first prompt of the task.
- The session note is a retelling. — Cut it to what was decided and what changed. Then halve it again.
- The cold session cannot continue. — Add the missing fact to the note and test in a new session again.
Share what happened
Paste the full path the artifact landed at, the session note in full (with the archived transcript's path), its word count against the raw transcript, and how each of the three cold-start questions went.
Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].
🔒 Don't paste confidential, personal-health, or payment info.