Agent Project File Delivery

Operations colleagues need to organize a batch of scattered materials into an index, summary, and delivery files. To avoid accidentally changing the originals, make the Agent's working directory, editable scope, and acceptance method clear in advance.

Suitable tasks

• Organize scattered materials into a table of contents and index;
• Generate multiple documents based on a template;
• Modify code and leave change notes;
• Batch rename, convert, or check files.

The Agent workspace puts the task, model, working directory, and deliverables on the same page.

For long tasks, first check whether the [Status] panel is running, waiting for approval, or already completed.

After the deliverables are generated, actually open them and check. The webpage preview in the image already shows the title, check items, and suggestions, not an empty placeholder.

Workflow

1

1. Choose the smallest working directory

Only select the current project directory. Important files should first have backups or version records, and permissions should start with [confirm each time].

2

2. Clearly define what can and cannot be changed

Specify which files are read-only, where outputs should be placed, which operations must be confirmed first, and the completion criteria.

3

3. Let the Agent list a plan first

For high-risk tasks, you can use [planning only]. After confirming the file list and steps, switch to a mode that allows editing to execute.

4

4. Check status and files on the right

For long tasks, first check whether [Status] is waiting for approval; after outputs are generated, preview them in [Files]. Only hand them over after confirming they are correct; do not use 'task completed' instead of acceptance.

Example task

Organize the current directory. Files in raw/ are read-only; create an index, summary, and missing-materials list under deliverables/. Any deletion, overwrite, or batch renaming must first be confirmed. Finally, list the newly added and modified files.

Recommended combination

Capability	Recommended usage	Why
Working directory	Use a separate directory for each project	File boundaries and delivery locations are clear
Permissions	Keep file modifications in [confirm each time]	Helps detect accidental deletion, overwriting, and out-of-bounds writes
Status panel	Check outputs and failed steps before finishing	Do not rely solely on 'the Agent said it was done'
New task	Open a separate task for a new phase or a new client	Avoid historical requirements affecting current delivery

[Full access] will reduce confirmations, but it will also increase the impact of misoperation. Consider using it temporarily only in isolated, trusted, and recoverable directories.