Keeping the files for one job together

A project is a folder for one piece of work: a launch, a client, a rebuild. You put the files in once, and every chat you start inside it has already read them. No attaching, no reminding it which document you meant.

Projects is in the sidebar, under Classroom.

Start one

Press New project and give it a name and a line saying what it is for. That is the whole setup. You can add instructions later — a note in your own words about how to work in this project, which every chat here follows:

Answer as the launch lead. Use the pricing in the files, never older numbers.

Put the work in

Three doors, all in the Context panel on the right of the project:

1. Upload files. Drag them in or use Add → Upload files. PDFs and Word documents have their text pulled out as they upload, so what is in them is readable, not just the file name.
2. Paste text. For something you have in your clipboard and not in a file — a pricing note, a policy, the wording you keep reusing.
3. Add a video link. Paste a YouTube, Loom or Tella link. Cook fetches the transcript, saves the video itself when the platform allows it, and writes a description of what is on screen. About a minute.

What “in context” means

Each file in the panel says how it is used:

• In context — its words are read in full at the start of every chat in this project.
• Read on demand — it stays in the project and is opened when a question needs it. Pictures and videos sit here; so does text once the project holds a lot of it.

The bar at the top of the panel shows how much is riding along, like 170K / 200K. When you pass the limit, the newest text files move to read on demand rather than being dropped — nothing is lost, it is just opened when needed instead of every time.

For a video, the transcript and the written description are the part that rides along; the clip itself is opened only if you ask something the words do not answer.

Then just ask

Type the question in the project’s own box, in the words you would use with a person. No file names, no commands:

what did the april webinar offer cost? i need the normal price, the cohort price and whether there was a deposit

The answer comes back with the numbers and the file each one came from, because the files were already read — there is no searching step in between.

What else lives in a project

• Its chats. Every conversation you start on the project page is listed there, so the thread from three weeks ago is where you left it.
• Its memory. Anything worth keeping that comes up in those chats is written down and shared with your workspace. It fills in as you work.
• Its routines. A routine you build from a project chat is filed under the project, and its runs read the same files.

Housekeeping

• Rename a project whenever you like; its files stay put.
• Archive it when the work is done. It leaves the Active list and nothing is deleted — restore it and it comes back exactly as it was.
• Remove a file from the panel and it leaves the project’s reading, but the drive keeps every version.

If a project is not in your sidebar yet, it has not been switched on for your workspace. Ask in a chat and Cook will tell you where you stand.