Working with filesFrom the window to the file · 7 min read

The idea that changes everything

In the browser, the conversation is the work: everything you achieved lives inside that thread. If it closes, if it fills up, if you cannot find it again, you lost it. That is why it feels cramped.

Here the conversation gets demoted: it becomes the channel you give instructions through. The work does not stay there — it stays in files, on your disk.

IN THE BROWSER

You the conversation ✕ nothing left

The work lives inside the conversation. Close it and nothing is left.

WITH FILES

You the conversation the file

The conversation only gives instructions, and is disposable. The file stays on your disk.

The difference is a single node: a place appears where the result lands and stays.

The limit is the folder. The AI only sees what is inside the one you opened. It does not see the rest of the disk, or your photos, or your mail, or whatever you have in another window.

This is not a technical limitation somebody forgot to fix: it is the protection. That is why the gesture for starting work will always be the same — open a folder, not a loose file.

And even inside that folder, it will ask permission before touching anything.

Three habits for day one. These are not information-security rules: they are what makes the experience good.

  1. Ask for the plan before the action. "First show me what you are going to do, do not do it yet." You read the plan, and only then tell it to go ahead. You will use this constantly at the start and less and less afterwards.
  2. Never delete: move. The standing instruction is that instead of deleting, it sends whatever is left over to a separate folder and tells you. You look later and delete by hand. You will never lose something to a misunderstanding.
  3. New topic, new conversation. A conversation with too many things mixed into it starts giving odd answers — and that is the number one cause of "but it was working before".

What you do NOT have to do, to lower the anxiety before starting:

  • You do not have to learn commands. You talk to it in plain English.
  • You do not have to understand what "git" is. It gets installed because it is needed underneath, but you will not touch it.
  • You do not have to prepare anything in advance. We install together, from scratch.
  • You cannot break anything important. The folder will be synced with version history, and habit number 2 handles the rest.
  • You do not have to remember any of this. If something was not clear, that comes back later already in use. There is nothing to study.

You close the window and shut down the machine. Where did the work go?

The conversation is disposable. The file is the memory.

snack 3 of 9 · Text or binary

Powered by KlugerByte