The Agent File System gives agents your organization as files they already know how to navigate.
The Agent File System is your organization laid out as folders and files for Ventos agents to work in: accounts, people, projects, memory and skills. Agents don’t search it for fragments. They open the folder, read the document and follow the reference, the way a person would, because today’s models were trained on exactly that kind of navigation in codebases.
What it means for your org
Answers built from whole documents
Ask about the Acme renewal and the agent can go to the account, open the agreement, read it through and follow references to the meeting notes beside it. The answer comes from the document in context, instead of a few lines lifted out of it.
The synced copy stays read-only
Inside the file system, the synced copy of your CRM records and documents is read-only. Within your organization’s knowledge, agents write only to memory and skills, so what your team relies on stays as it arrived. Any change to a source system is a separate action you confirm.
See exactly what your agent sees
The explorer lets people browse the same folders and files their agent works from, with the same permissions. When an answer surprises you, open the document behind it and check.
Teach it how your team works
Write down how your team prepares for a board meeting or onboards a new hire, and agents follow it from then on. Procedures live as skills next to the knowledge, with no engineering work or deploy to get them running.
How it works
- 01
Built on what models already know
Models have spent their training listing folders, matching file names, searching for a phrase, opening a file and following a reference to the next one. Ventos does not teach an agent a new retrieval API. It lays your organization out the same way. The Company Brain holds what your organization knows; the file system is the structure agents use to move through it.How we built it: why the file system runs on a proven database →
- 02
Retrieval vs. navigation
A retrieval-only (RAG-style) setup splits documents into fragments and returns the closest matches, and the model answers from those pieces without the rest of the document. Ventos agents use both search and navigation.When an agent roughly knows where to look, it navigates: list a folder, match names, search the text, read. When it does not, it runs hybrid semantic and keyword search across the knowledge, scoped by folder and date. Search finds the place, and navigation lets the agent read the whole document in context, along with what sits next to it.
- 03
One document, many places
A renewal agreement belongs to the account, to the project tracking the renewal and to the person who owns the relationship. The file system stores it once and makes it reachable from each of those places, so the agent finds it from whichever direction it starts. See what agents do with it in the Ventos product.
- 04
Skills sit next to the knowledge
Skills are files in an open format kept beside the knowledge they apply to. Some are org-wide, some belong to one person, and agents can write new ones as they learn how the team works. A proactive agent that runs on a schedule or responds to an event reads the same skills a person’s agent does.
- 05
Files, plus a private workspace
The file system holds PDFs, spreadsheets and images alongside text. Each person also has a private workspace, a sandbox where their agent can run analysis or code on files next to the org’s knowledge, using the same file tools it uses everywhere else.
Agents cannot edit the synced copy of your records and documents.
Browse exactly what the agent sees, under the same permissions.
Changes to memory and skills are logged with who made them and where.
Proactive Agents
Agents that work without being asked
Read moreWatch an agent find its way around your organization.
In 20 minutes we’ll walk through how agents navigate and search the systems your team already uses.
Book a 20-min call