Eyra treats local file work as computer control. Paths are resolved under the filesystem sandbox, writes are bounded, overwrites require explicit consent, and reversible operations record undo metadata when possible.

​
Sandbox

FILESYSTEM_ALLOWED_PATHS=~/Documents,~/Desktop,~/Downloads,/tmp
FILESYSTEM_DEFAULT_PATH=~/Documents
Relative paths resolve under FILESYSTEM_DEFAULT_PATH, then Eyra checks the resolved path against FILESYSTEM_ALLOWED_PATHS.

​
Supported file actions

ActionTool
Read textread_file
Write new filewrite_file
Edit textedit_file
Append or prependappend_file, prepend_file
Compare text filescompare_files
List directorieslist_directory
Create directoriescreate_directory
Move or copymove_path, copy_path
Rename or duplicaterename_path, duplicate_path
Compress or extractcompress_path, uncompress_archive
Move to Trashmove_to_trash
Restore from Trashrestore_from_trash
Delete permanentlydelete_permanently
Reveal or openreveal_path, open_path
Extract PDF textread_pdf

​
Safer defaults

  • Existing files are not overwritten by default.
  • Permanent delete requires approval.
  • Trash is preferred for removal.
  • Binary reads and edits return clean messages instead of raw bytes.
  • Archive extraction stays under the sandbox.
  • Browser downloads and uploads stay sandboxed when network tools are enabled.

​
Deterministic file intents

Common file requests can run before model tool loops: 
Move the latest downloaded file to Documents.
Rename report-final.pdf to report.pdf.
Undo that.
No, I meant report-draft.pdf.
Eyra resolves named folders such as Desktop, Documents, Downloads, Pictures, Movies, Music, and /tmp, then records the operation.

​
Operation ledger

Computer-changing actions record observe, plan, act, verify, and recovery details in the local ledger. Inspect it with: 
/operations
Ask: 
What changed?
Undo that.
Undo is available only when Eyra has enough metadata to reverse the operation honestly.