Workspace files and artifacts

Neo can read and modify files in an available workspace and create organized artifacts such as Markdown documents, reports, configuration files, and structured datasets.

What is a workspace?

A workspace is the bounded set of files and tools Neo can access for the current task. Access does not imply that every file should be changed. State the allowed scope and preserve unrelated work.

Safe collaboration pattern

1. Ask Neo to inspect the relevant files.
2. Request a plan and identify files it may change.
3. Approve focused edits or authorize reasonable execution.
4. Review the diff or resulting files.
5. Run tests or validation checks.
6. Keep a record of what changed.

Inspect before editing

Read the documentation folder and identify broken links, duplicate pages, and missing navigation entries. Do not edit anything yet. Return findings with file paths and a proposed fix order.

This lets you correct a wrong understanding before files change.

Bound the edit

Specify:

• files or directories Neo may inspect;
• files it may create, edit, move, or delete;
• formatting and naming conventions;
• generated or vendor files to avoid;
• tests or validation required;
• whether existing behavior must be preserved.

Artifact delivery

When Neo creates a file, ask for its name, location, format, and a short description. Open the artifact to confirm it is readable and contains the expected information. For structured outputs, validate the schema and sample records.

Destructive operations

Deletion, replacement, bulk renaming, irreversible conversion, and broad search-and-replace require extra care. Ask for a preview or file list first. Keep backups or version control for important work.

Review the result

A successful edit should be limited to the requested scope, consistent with nearby conventions, and validated with the relevant checks. Neo should report blockers or skipped files rather than silently guessing.