Projects & folders

A project is a scoped window. It binds a set of files, a standing instruction note, and its own chats — so every conversation inside it starts briefed with your context instead of empty: loaded whole while the pile is small, searched for the relevant parts once it outgrows the window. That's the entire feature: loading the window, automated — with the app deciding what fits.

Do it now, in your own account: create one project for something real. Drop in two or three source files — the plan, the key document, the current state. Write one paragraph of standing instructions: who you are, what this project is, what good output looks like. Every chat you open there now starts warm.

Folders are the same move for tools that read and write your files. A folder on disk holding the project's files, a running journal, and a note about the current goal is a project the command line can walk into cold — the breadcrumbs make any fresh window situationally aware in seconds.

The test of a good project or folder: could a brand-new chat, with no history, pick up the work from what's in there alone? If yes, you've built a workspace that briefs every window it opens. If no, you've built a junk drawer.

Say it back in one line: what does a project actually do to the window?