AppsDrive

AI agents on your files · Autessa Drive

Drive tools for agents

Autessa Drive gives AI agents permission-aware file tools. Bind a drive to an agent, or create a Drive tool, and the agent receives one narrow tool per operation: list, outline, find, details, grep, read, search and fetch, plus write, edit, make folder, move and trash when you allow writing. Every call only reaches files the acting person can open.

Goes beyond a typical cloud drive
Start free
Agent · Contracts assistantDrive: Acme LegalSAMPLE

Tools the agent receives

drive_lsdrive_treedrive_finddrive_statdrive_grepdrive_readdrive_searchdrive_fetchdrive_writedrive_editdrive_mkdirdrive_movedrive_trash
■ read■ write (needs Editor)
Acting identityThe person chatting
Folder scope/Legal
Semantic searchOn

the-problem.md

Agents either see nothing or everything

Most AI document Q&A copies files into a separate index that ignores who is allowed to see what, or gives a bot a service account with access to all of it. Agents need the same permissions as the people they help, and tools precise enough to find the exact clause.

README · what you get
  • Every file operation an agent needs: ls, tree, find, stat, grep, read, search, fetch, write, edit, mkdir, move and trash.
  • An agent bound to a drive receives them as drive_ls, drive_grep, drive_read and so on, with guidance to search for topics, grep for exact strings and read before quoting.
  • A single Drive tool can be configured for one operation, with arguments the agent fills at run time.
  • read returns numbered lines for a page or line range; grep returns path (vN) pPage:LLine matches; search returns ranked passages.
  • fetch returns a 10-minute download link, and with view on shows up to 5 pages or an image to the model.
  • write, edit, mkdir, move and trash need Editor access for the acting identity, and every write is a new version.
  • Errors such as EDIT_NO_MATCH, EDIT_AMBIGUOUS and VERSION_CONFLICT carry a hint naming the next call.
  • A Search agent can also use a drive as its Knowledge Base Table.

how-it-works

How does drive tools for agents work in Autessa Drive?

  1. 1

    Pick the drive

    Create a Drive tool for it, or choose the drive as a Search agent’s knowledge base.

  2. 2

    Choose read or write

    Read tools are the default; add write tools when the agent should create or edit files.

  3. 3

    Optionally fence it

    Set a folder scope such as /Legal so the agent can see only that part of the drive.

  4. 4

    Ask

    The agent searches, greps, reads the page and answers with citations.

every-option

Agent operations

OptionWhat it does
lsList a folder, folders first (path, limit, cursor, sort).
treeOutline a folder and its subfolders (maxDepth, maxEntries).
findBy name, glob, regex, type, file type, dates or size.
statSize, version, page count, processing status.
grepExact string or regular expression, with context lines.
readA page range or line range.
searchRanked; meaning-based when semantic search is on (topK).
fetch10-minute link; view shows pages or images to the model.
write / editText files up to 5 MB; overwrite, create or append; exact replace with expectedVersion.
mkdir / move / trashFolders, moves and renames, and trash.

permissions

Who can do what?

WhoCan
Agent with a Drive toolUse the operations it was given, only on files its acting identity can open.
EditorTheir agents can write where they have Editor access.
ViewerTheir agents can read what they can read, nothing more.
Drive owner and drive adminsTheir agents see the whole drive unless a folder scope narrows it.

AI agents

How AI agents use it

This page is the AI assist. The tools are deliberately narrow, so a model makes small, checkable steps: find the file, grep the clause, read the page, then answer and cite.

Agents only reach files the person they act for can open, and every agent write is a version you can undo.

About Drive tools for agents →

connected

How it connects to the rest of Autessa Drive

DRIVE FEATURE

Cited answers

How agents quote what they read.

DRIVE FEATURE

Folder scope

Confine a tool to one folder.

DRIVE FEATURE

Memory files

Agents that write and remember.

AUTESSA PRODUCT

Autobots

Chat with an assistant that reads your drive.

faq.md

Questions about drive tools for agents

Can an AI agent read files in Autessa Drive?

Yes. Bind a drive to the agent or create a Drive tool, and it can list, find, grep, search, read and fetch files, only those its acting person can open.

Can agents change files?

Only if you give them write tools, and only where the acting identity has Editor access. Every write and edit is a new version you can restore.

Can an agent look at images or scanned pages?

Yes. drive_fetch with view on shows up to 5 pages or an image to the model, for charts, photos and scans.

Is this the same as a knowledge base?

A knowledge base is a flat table of files indexed for semantic search. A drive has real folders, page- and line-level search, versions, trash, per-folder sharing and these file tools. A Search agent can use either.

Autessa Drive

Try drive tools for agents in Autessa Drive

Autessa Drive gives AI agents a full set of narrow file tools, from ls and grep to read and edit, that only reach files the acting person can open.

Start free

100% customizable, code and all

Make Autessa Drive fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours