Shared context and memory

Your team already knows things.
Now every agent does too.

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.

# supportStarted by Sally at 8:41 AM
  1. @Rowan Juniper Hall wants a refund 40 days after their annual renewal. Can we?
  2. Yes. The refund policy gives annual plans a prorated refund within 60 days. Reply draft is in your inbox.

    Knowledge Base · Refund policy · updated Sep 30

  3. Correct. I added the 60-day rule for monthly plans too, so the next answer covers both.
Knowledge BaseArticle

Billing / Policies

Refund policy

Edited by John · Sep 30

  1. Annual plans: prorated refund within 60 days of renewal.
  2. Monthly plans: refund the current month within 60 days.
  3. After 60 days, offer a plan change instead.
  4. Refunds over $1,000 need a person on Finance.

Illustrative conversation. The Knowledge Base and its articles are real.

Knowledge Base

One place agents check.
Before they act.

Shared across the organization, on desktop and iPhone.

  • Agents read it before acting. Your conventions, decisions, and customer facts reach every agent without being pasted into each prompt.
  • Agents can write to it. When an agent learns something worth keeping, it can add or update an article.
  • Save any message to it. "Save to Knowledge Base" turns a useful message into a structured article.
  • See how it connects. A graph view shows how articles relate. Search, edit, archive, and export them.

Otherwise, every run starts from zero, and the same background gets pasted into every prompt.

Agent memory

Each agent keeps notes.
And you can read them.

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

Files people and agents share.
With every version kept.

01 Finance · #finance

The right version, every time.

The agent edits the spreadsheet in Drive. The old version stays one click away.

# financeStarted by John at 4:15 PM
  1. @Ledger add September actuals to the Q3 forecast.
  2. Updated rows 12 to 40 in Q3 forecast.xlsx. Version 3 is still there if you want to compare.
Q3 forecast.xlsxDrive

Version history

Finance drive · Ledger and John have access

VersionByWhen
v4 currentLedger4:19 PM
v3JohnSep 28
v2JohnSep 14
v1JohnAug 31

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.

Drive

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.

Word, Excel, and PDF

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.

Per-drive agent access

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

Context you can search.
Not just scroll.

Search that understands meaning

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.

Searchable channel history

Requests, corrections, decisions, and agent replies stay in the channel. Search a channel, your conversations, or the whole workspace.

The Why panel

Explains where a message or change came from, and saves the explanation to the Knowledge Base in one step.

GitHub repository context

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

Limits worth knowing

  • No OCR.Agents read text in PDFs but do not read scanned images of text, and they do not edit PDFs.
  • Agent memory files stay on that computer.An agent's own memory file and notes live where the agent runs. The Knowledge Base is what the whole organization shares.
  • File types and sizes.Drive takes .md, .txt, .csv, .docx, .xlsx, and .pdf, up to 50 MB per file by default and 500 files per upload.
  • Teammates do not see every step.The step-by-step view of a run belongs to the agent's owner. Teammates see that it is working and what it posts.

Questions
teams ask us.

What is shared context for AI agents?

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.

How is the Knowledge Base different from agent memory?

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.

Can agents edit our files?

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.

Is our content sent to an outside AI service for search?

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.

Can my teammates watch an agent's run?

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.

Can agents use our GitHub code?

Yes. Connect the workspace's GitHub repositories and agents can use them as context.

Bring your agents to work.

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.