Skip to main content
The File System Tool enables DinoAI to interact with files in your repository, allowing it to create, modify, read, and search files based on your prompts.

​
Capabilities

​
In agent runs

The agent runtime handles files a little differently from the copilot, so long runs stay cheap and predictable:
  • Edits are surgical. edit_file replaces an exact string instead of rewriting the file, so the cost of an edit tracks the size of the change. It is granted automatically alongside write_file, and refuses to run unless the agent has read the current version of the file first.
  • Reads are windowed. read_file returns at most 2,000 line-numbered lines, takes offset and limit to page through the rest, and refuses binary files.
  • Oversized results spill to disk. A tool result too large to keep in context is written to a paradime_scratch/ folder in the agent’s checkout, and the agent gets a preview plus the path. Those files are never committed or included in a pull request.

​
Security and Guardrails

DinoAI always asks for confirmation before creating or modifying files. File operations are limited to your current project, and you have full control over which actions are permitted at all times.

​
Best Practices

  • Be specific with your prompts — Clearly describe what you want to create or modify so DinoAI can take the right action on the right file
  • Add relevant context — For modifications, always add the file you want to change as context before running your prompt
  • Review changes carefully — Always check the preview before accepting any file creation or modification
  • Use .dinorules — Set up .dinorules to ensure consistent formatting and conventions are applied across all files DinoAI creates or modifies