AppsAutessaDB

Files, apps and operations · AutessaDB

Drive on AutessaDB

An AutessaDB Drive is a table of files and folders. Because it is built on AutessaDB, files get the same sharing, the same agent tools, the same CLI and the same SDK as every other table: browse, grep, read, search, push and pull folders, version files and share them with people, teams or the company.

Goes beyond a typical managed database
Drive · Legal/Shared/Legal/ContractsSAMPLE
nametypeversiontext
2026/FOLDER
acme-msa.pdfFILE2EXTRACTED
globex-msa.pdfFILE1EXTRACTED
autessa drive grepSAMPLE
/Shared/Legal/Contracts/acme-msa.pdf:4:12: 12.2 Termination for Convenience…
/Shared/Legal/Contracts/globex-msa.pdf:7:3: 9.1 Termination for Convenience…

-- the problem

Files and data usually live in different systems

Contracts in one drive, the contract register in a database, and an agent that cannot see both. When files live in AutessaDB, an agent can grep a clause, read the page, and update the record in the same breath, under one set of rules.

What you get

  • Folders, file versions, trash and restore, comments and share links.
  • Shares at VIEWER, COMMENTER or EDITOR for people, teams, Drive members or the whole company.
  • grep for exact text or regular expressions, with path:page:line output.
  • Ranked search that is meaning-based when the Drive's semantic search is on.
  • push and pull whole folders from the terminal, with .autessaignore and checksum checks.
  • A move that would change who has access asks for confirmation first.
  • The AUTESSADB_DRIVE agent tool gives agents ls, tree, find, stat, grep, read, search and text writes.

-- how it works

How does drive on autessadb work in AutessaDB?

  1. Create a Drive

    New, then Drive, from the AutessaDB tables list.

  2. Fill it

    Upload in the explorer, or autessa drive push a local folder.

  3. Share

    Share folders with teams or members at the right role.

  4. Put agents on it

    Give an agent the Drive tool to find and read documents.

-- every option

Drive basics

optionwhat it does
RolesVIEWER, COMMENTER, EDITOR, plus Drive managers.
push --onConflictFAIL (default), RENAME or NEW_VERSION.
push --mirrorAlso trash Drive files no longer in the local folder.
LinksView-only share links, company-only or public.
Semantic searchA Drive setting that makes search meaning-based.

-- example

Drive shorthand in the CLIbash
autessa drive use Docs
echo "- Acme prefers Net 45" | autessa drive append notes/memory.md
autessa drive edit notes/memory.md --old "Net 45" --new "Net 60"
autessa drive grep "Net 60" notes/

Full reference in the AutessaDB CLI docs and the API reference.

-- permissions

Who can do what?

accesscan
Drive managerManage members, settings and every file.
EDITOR / COMMENTER / VIEWEREdit, comment on, or view what is shared with them.

-- relations

How it connects

-- faq

Questions about drive on autessadb

Is Autessa Drive part of AutessaDB?

Yes. A Drive is an AutessaDB table of files and folders, which is why it shares AutessaDB's agent tools, CLI and SDK.

Can agents read files in a Drive?

Yes, with the Drive tool type, and only the files the identity they run as can open.

Can I sync a local folder?

Yes. autessa autessadb drive push uploads a folder and pull downloads one, verifying checksums.

Also in Files, apps and operations:Backend for custom appsSoft delete and restore

$ autessa autessadb tables create

Try drive on autessadb in AutessaDB

A Drive is an AutessaDB table of files and folders, so files get the same access rules, agent tools, CLI and SDK as every other table.

Read the AutessaDB guide or install the CLI.

100% customizable, code and all

Make AutessaDB 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