GuideKeep a folder to one agent

A quiet lock on a folder.

A fence keeps a vault folder to the agent you name. Every other agent — your everyday assistant included — simply never sees that the folder is there. You see everything, always.

3 chapters
In this guide· 3 chapters
What a fence is

It governs your agents, never you

When you give a specialist agent something private — a health keeper, a coach, a journal — you want "only this agent can open it" to be literally true. A fence makes it so for the vault. The folder stays exactly where it is; what changes is who can walk in.

To an agent outside the fence there is nothing to ask about. The folder is not "locked", it is absent: it does not appear in listings or search, and a file inside it reads as not found. Your everyday assistant is not an exception — it is usually the one you most want kept out.

You are never fenced. The explorer, search, downloads, sharing, version history and the bin all behave as before — with a padlock and the keeper’s mark on the folder so you can tell what is kept, and by whom.

Setting one

Three ways to set a fence

From the folder’s page. Open any folder in your vault. Under its memory line you’ll see "Open to your agents · Fence this folder". Tap it, tick the agents that may open the folder, and save. Tick nobody and the folder is kept for you only.

In conversation. Ask an agent to keep a folder to itself — "keep this folder between us" — and a card appears in the thread naming the folder and the agent. Nothing changes until you confirm on the card.

When you set up an agent. If you give a new agent memory that is set apart from your other agents, you’ll be offered a folder of its own at the same moment. Say yes and its notes stay with it from the first one.

Say this

Keep the Journal folder to yourself.

A card names the folder and the agent; confirm, and the padlock appears on the folder.

Say this

Who can open my Health folder?

The keeper agent answers plainly; any other agent cannot see the folder to answer at all.

Living with it

What changes, and what doesn’t

Memory follows the fence. A fenced folder that is remembered in full is remembered by its keeper alone, so nothing from it surfaces in another agent’s recall. If more than one agent keeps a folder, or its keeper shares memory with the others, the folder stays searchable rather than remembered — the folder page says why.

Moving files. The keeper can tidy inside its folder but cannot carry a file out of it; that is yours to do, from the explorer. Files you send to the bin from a fenced folder come back under the fence.

Synced folders are different. A folder that mirrors one on your computer or in Google Drive is a copy of somewhere else, not a private room, so it can’t be fenced — and a fenced folder can’t be chosen as a sync destination. Move the files into a folder of their own to keep them.

Sharing is still yours. You can share a document from a fenced folder with a person exactly as before; the share sheet just reminds you that doing so sends it outside the fence.

Changing your mind. Open the folder’s page and tap Manage to add or remove agents, or remove the fence altogether. An agent’s Access tab lists the folders it keeps, too. Only you can remove a fence — no agent can ask its way out of one.