Organise files and repeatable workflows safely

File operations are the one place where a mistake is not recoverable by pressing undo. The safety routine is short and worth making automatic.

beginner8 minChecked 2026-09-06

What you will be able to do

Run a file-organising task with an agent without risking anything you cannot recover.

Before you start

  • A folder that needs work.
  • Somewhere to put a copy.

Copies, always, at first

The first run of any file-changing task happens on a duplicate. Not because the tool is unreliable, but because your instruction may be — and an ambiguous instruction executed thoroughly is the risk.

Dry run before wet run

Ask for the plan: every file it intends to touch, current state and proposed state, in a list. Read it. The plan is where you discover that "invoices" also matched a folder of drafts.

Rules that prevent the bad outcomes

Never delete — move to a holding folder instead. Never overwrite without stopping to ask. Flag ambiguity rather than guessing. Keep a log of what changed.

These four instructions turn a risky operation into a reviewable one.

Step by step

  1. Copy the folder. Work on the copy.
  2. Write the rule as an outcome with a worked example of the naming or structure you want.
  3. Add the four safety rules: no deletion, no overwrite without asking, flag ambiguity, log everything.
  4. Request the plan and read it in full.
  5. Approve, then spot-check ten results against the rule.
  6. Only then consider running it on the original.
Safe file-organising brief
Work only in the folder I have selected.

Outcome: every file is filed into a subfolder named YYYY-MM by the date in its filename or metadata.

Rules:
- Never delete. If something must go, move it to _needs-review.
- If a move would overwrite an existing file, stop and ask.
- If a date is ambiguous or missing, move the file to _needs-review rather than guessing.
- Write a log listing every move as from → to.

Before doing anything, show me the full plan.

What good looks like

  • A log exists and matches what happened.
  • Nothing was deleted.
  • Ambiguous cases are in a review folder rather than filed wrongly.

What it cannot do

  • It cannot judge whether a file matters.
  • It cannot undo an overwrite, which is why the rule exists.

When it goes wrong

Files filed under the wrong date.
The date source was ambiguous. Specify which source wins — filename over metadata, or the reverse.
A rename collision lost a file.
The overwrite rule was missing. It belongs in every file-operation brief.

Privacy and data handling

Only point an agent at folders you are entitled to share. Client files, HR records and health information usually need a specific approval that a general plan does not provide.

Sources3 referenced
  1. Claude Cowork — product page

    Anthropic · official product documentation · link checked 2026-09-06

  2. Guidance on AI and data protection

    Information Commissioner's Office · regulatory guidance · link checked 2026-09-06

  3. Guidelines for secure AI system development

    National Cyber Security Centre · security guidance · link checked 2026-09-06

Links are checked at build time. If one has moved, tell us.

Written by
BLACK LDN
Last checked
2026-09-06
Content state
editorial

Product behaviour changes. If something here no longer matches the documentation, send a correction.

Read next

Choosing a tool9 min

Claude Cowork: from request to finished files

A different shape of assistant. Instead of a conversation you copy out of, you hand over a task with a scope and get reviewable work back.

beginner

Checked 2026-09-06

Using it responsibly9 min

Privacy and sensitive information

The question is not whether these tools are safe. It is what you are permitted to put into them, and what happens to it afterwards.

beginner

Checked 2026-09-06

Next: Research and learn with a verification trail