Corey Corey
Hire Corey
How it works Use cases Guides Build log What Corey builds Docs Hire Corey

File and folder tools

Corey can read, write and organise files in your Corey folder and any directories you approve. It works on real files - drafts, exports, documents - so the output of a job lands where you can use it, and it never reaches outside the paths you have allowed.

Corey produces real output - documents, drafts, exports, plans - and it needs somewhere to put them. File and folder tools let it work directly with files on your computer, reached over MCP, so the result of a job lands where you can use it rather than trapped in a chat window.

It works in two places: the Corey folder (its home base, where it keeps your business context and the work it produces) and any other directories you approve. It never reaches outside the paths you have allowed.

What Corey can do with files

Within the paths you allow, Corey can:

  • read files to understand context - existing documents, notes, exports
  • write new files - drafts, plans, reports, generated assets
  • edit files it or you created, in place
  • organise your folder - create directories, move and rename files, keep Projects tidy

Everything it creates is a real file you can open, edit or move yourself.

The Corey folder and approved paths

The Corey folder is the default workspace. Corey reads and writes here freely because it is yours and it is where your context lives.

To let Corey work elsewhere - a documents folder, a code repository - you grant that path explicitly. Access is opt-in, one directory at a time, and anything outside your approved paths stays out of reach.

What stays behind an approval

Reading and organising are safe and run without interruption. The actions that can lose work are treated as irreversible and wait for you:

  • overwriting a file that already has content
  • deleting files or directories

Before any of these, Corey tells you what it intends to change so you can confirm or redirect. This is the same approval model that runs across every tool: read-only steps run freely; anything irreversible waits. See best practices for how to set those guardrails.

Where your work lands

Corey keeps output organised in your folder, grouped by Project, so a finished invoice, a drafted page or a research summary is a file you can find, not a message you have to scroll back to. Because it is plain text and standard document formats, you stay in full control of everything Corey makes.

Related

Questions, answered

In a folder on your own computer - the Corey folder - plus any other directories you explicitly approve. Nothing is stored on Corey's servers. The files are plain text and documents you own and can open, edit or move yourself at any time.
Only with your approval. Reading and organising run freely, but anything destructive - overwriting or deleting - is treated as irreversible and waits for your nod. Corey shows you what it intends to change before it acts.
Only the directories you have granted. Corey cannot read or write outside the paths you have allowed, so the rest of your computer stays off limits unless you choose otherwise.