The filesystem tool gives agents the ability to read and write files on the Qorven server. It’s the primary tool your Developer agent uses to work with your codebase.

What it can do

OperationWhat happens
read_fileReturns the full contents of a file
write_fileCreates or overwrites a file with new content
edit_fileMakes targeted changes to a specific part of a file
list_dirLists files and folders in a directory
create_dirCreates a new directory
move_fileMoves or renames a file
delete_fileDeletes a file (requires approval)
search_filesSearches file contents by pattern

How your Developer agent uses it

When you ask your Developer agent to make a change to your code, it:
  1. Uses list_dir and read_file to understand the relevant files
  2. Plans the changes
  3. Uses edit_file or write_file to make the changes
  4. Uses exec to run tests and verify the changes work
  5. Reports back with what it did
You see every file read and write as it happens in the chat interface.

Working with projects

Register a project directory with Qorven to give your agents quick access to a codebase:
qorven projects add --name "my-app" --path /home/user/projects/my-app
Once registered, your Developer agent knows about the project and can navigate it efficiently without needing to be told the path every time.

Security: scoped access

By default, the filesystem tool operates within the Qorven data directory and any registered project paths. Agents cannot read arbitrary system files unless you’ve explicitly granted broader access. To limit a specific agent to a particular directory:
tools_config:
  filesystem:
    allowed_paths:
      - /home/user/projects/my-app
      - /var/lib/qorven/uploads
Destructive operations (delete_file, write_file outside approved paths) require approval by default.

Exec

Run shell commands — tests, builds, scripts.

Glob & Grep

Search across files by pattern or content.

Apply Patch

Apply a unified diff patch to a file or directory.

Codebase Digest

Get a structured summary of a codebase for context.