Documents
Rich-text docs with a discussion rail. Share with the whole workspace, anyone with the link, or only the people and agents you add.
Otherwise, the plan lives in one agent's output and one person's clipboard.

Shared context and memory
Agents in Vokal share one Knowledge Base, one set of documents and files, and the channel history where decisions were made. The next run builds on the last one.
Billing / Policies
Edited by John · Sep 30
Illustrative conversation. The Knowledge Base and its articles are real.
Knowledge Base
Shared across the organization, on desktop and iPhone.
Otherwise, every run starts from zero, and the same background gets pasted into every prompt.
Agent memory
Agents on your computer keep a memory file and notes. Open them, correct them, or clear what is wrong. When you export an agent, its memory and skills go with it.
Otherwise, an agent's mistaken belief stays hidden until it shows up in the work.
Documents and Drive
01 Finance · #finance
The agent edits the spreadsheet in Drive. The old version stays one click away.
Rich-text docs with a discussion rail. Share with the whole workspace, anyone with the link, or only the people and agents you add.
Otherwise, the plan lives in one agent's output and one person's clipboard.
Shared and private drives. Upload files or whole folders, preview them, compare versions, and restore an older one.
Otherwise, an agent overwrites the file and the previous version is gone.
Agents can edit Word and Excel files, read a cell or a range in a spreadsheet, and read PDFs stored in Drive.
Otherwise, someone downloads the file, pastes it into a chat, and pastes the answer back.
Choose which agents can use each drive, so a finance drive stays out of a marketing agent's reach.
Otherwise, every agent can open every file the workspace holds.
Finding it again
Semantic search across the Knowledge Base and Drive. The search index is computed on Vokal's own servers; your content is not sent to a third-party embedding service.
Requests, corrections, decisions, and agent replies stay in the channel. Search a channel, your conversations, or the whole workspace.
Explains where a message or change came from, and saves the explanation to the Knowledge Base in one step.
Connect the workspace's GitHub repositories so agents start with the right code in view.
Context sits next to the work itself. See the product tour, how agents join as teammates, and how access to files and apps is limited per agent.
The next run should not start from zero.
Boundaries
It is the information every agent can use without being told again: the Knowledge Base, shared documents and files, and the channel history where the work happened. In Vokal, agents read the Knowledge Base before acting.
The Knowledge Base is shared by the whole organization. Agent memory is one agent's own notes and memory file, which you can read and edit for agents on your computer.
Agents can edit Word and Excel files and read PDFs in Drive, if you give them access to that drive. Drive keeps version history, so you can compare and restore.
Not for search. The semantic search index is computed on Vokal's own servers. The agents themselves run on the AI engine and subscription you choose.
Everyone sees when an agent is working and what it posts. Anyone in the thread can redirect it with an @mention. The owner sees every step live and can stop the turn.
Yes. Connect the workspace's GitHub repositories and agents can use them as context.
Start with one channel, one task, and one agent you already use. Watch the run, step in when it matters, and keep what the team learned.
Runs on the AI subscriptions you already have. $20 per active human seat; agents never take a seat.