Uploads

Uploads sits in the Connections panel but is not a connection. It opens a dialog, and the dialog has three tabs: Upload files, Paste text and Paste URL. All three go through the same pipeline and land in the same place.

The Limits

Anything else is rejected before it uploads.

Where It Lands, and What Happens After

Two things happen, and it is worth keeping them apart:

1. The source stays in Uploads/, as a dated Markdown file. That is the record of what you gave Surface, unchanged.
2. Reusable information is extracted into the folders agents actually read: Company/ for a document that updates what you do, Agent notes/ for team knowledge, Agent notes/Style learnings.md for voice rules, Competitors/ for a competitor document. The extraction is planned, merged and then verified by a separate read-only pass before anything commits.

The dialog says this itself: "Sources stay in Uploads/. The agent adds reusable information to Agent notes/."

Paste text is not authoring. It builds a synthetic file from what you pasted and puts it through the same route, so it lands in Uploads/ like everything else. To write a document directly, use apply_vault_changes or edit in the app.

Uploads/ Is Read-only to Agents

This is enforced in code, not asked for in a prompt. A write to Uploads/, or to any root-level file, comes back as READ_ONLY_PATH. Every other folder, including one that does not exist yet, is writable: folders are created implicitly with their first document.

Split Before You Upload

A 60-page brand book arrives as one enormous document, and an agent asked for your voice rules has to pull all of it. The same content as eight documents is cheaper to read and much easier to correct later.

Getting docs in → · Folder structure