Elliptic

The organization's Drive: upload documents once, file them in folders, and reference them from any task description, on the web, on the phone, and over the MCP.

One place for the documents

A note is a page you write inside Elliptic. A Drive document is a file you bring in whole: a countersigned contract, a floor plan, a supplier quote, a scanned form. The Drive is where those live, and it sits beside Notes for the same reason both exist — they are the reference material the work points at.

The Drive is scoped to the organization, not to a project. A signed agreement is read by the legal task, the finance task and the renewal task, so binding it to one project would turn every other reference into a copy. Folders keep it navigable instead, and every member of the workspace reads the same document.

Uploading and filing

Open Drive in the sidebar. Use Upload, or drag files onto the list. Bytes go straight from your browser to object storage over a signed URL — the same reserve, upload, confirm path attachments use — and the document then appears in whichever folder you are standing in.

Make a folder
New folder opens it immediately. A folder is a path carried by the documents inside it rather than a record of its own, so it exists once the first document lands there and disappears when the last one leaves. Nothing can be orphaned in it.
Upload into it
Whatever folder you are standing in is where the upload lands. Folders nest: open one and make another inside it.
Rename, move, delete
Each row's menu opens the document, copies its reference link, renames it, moves it to another folder, or deletes it. Renaming the open folder moves every document beneath it in one step.

Search reaches across the whole Drive, not the open folder — the point of searching is that you do not know where the document sits. A hit shows the folder it came from.

Size and type limits

A document may be up to 100 MB, and its content type must be on the upload allowlist (PDF, images, video, audio, plain text, CSV, Markdown, JSON, Word, Excel, PowerPoint, ZIP). Both are server settings — see Files, attachments & embeds for the full list and the self-hosting knobs.

Referencing a document from a task

This is what the Drive is for. In a task description, a project description, a note or a comment, type @ and start typing the document's name. Drive documents appear in the picker beside tasks and pages, tagged Drive and showing the folder they sit in. Pick one and it becomes a chip: a paperclip, the document's name, and a click that opens it.

The chip is stored as ordinary Markdown, so it survives copy, paste, export and an agent reading the description back:

markdown

Countersign and file the renewal.

Signed agreement: [Acme MSA 2026](/__mention/file/019eda44-8c2d-7e3f-9a01-223344556677)
Site layout: [Floor plan](/__mention/file/019eda44-9f01-7a2b-8c3d-445566778899)

Clicking the chip opens the Drive with that document selected, whether or not the reader has ever opened the folder it lives in. The document opens inside Elliptic: a panel that previews the file itself — an image, a PDF, the first few thousand characters of a text file, or a video or audio file playing in place — above the folder, file name, size and the date it was added. Nothing navigates away to storage. Download takes the file when you want the file, and Copy link puts the Markdown above on your clipboard for pasting into another description. Word, Excel and PowerPoint have no in-browser preview, so those offer Download alone. Full detail on the format is in References & mentions.

On the phone

The Notes tab carries a paperclip that opens the Drive. Folders walk in and out with the platform's own back gesture, and search reaches across the workspace. Tapping a document opens it in a sheet that reaches the top of the screen: a PDF or an image renders in place, and a text, Markdown, CSV or JSON document is served as text by the API. Drag the sheet down, or tap the close button, and the screen you came from is right there. Tapping a document chip inside a task description opens the same sheet over the task, so a link written on a laptop opens on a phone without losing your place. Word, Excel and PowerPoint have no phone preview — open those from the web app.

Reading, not uploading

The phone browses and reads documents; uploading is a web action. The documents that belong in a Drive arrive on a computer, and what the phone needs is the other half — reading the document a task points at, wherever you happen to be, without being thrown out to a browser to do it.

For agents (over the MCP)

Agents get the same Drive through the Company-Brain MCP, under two scopes: drive:read to browse and read, drive:write to upload, rename, move and delete. Read is part of the baseline grant; write is not.

Tool	What it does
`list_drive_files`	Browse a folder or search the whole Drive. Every item carries a ready-made `mention` string to paste into a description.
`list_drive_folders`	The folders, with how many documents each holds.
`get_drive_file`	One document's metadata plus a signed URL that lives for 300 seconds.
`read_drive_file`	The text of a text, JSON or XML document, a window at a time. A PDF or Office file reports `readable: false` and hands back a URL instead.
`view_drive_image`	An image document's actual pixels, so the agent can see it inline.
`create_drive_upload` → `register_drive_file`	The upload path: reserve a slot, PUT the bytes to the signed URL, then file the result under a name and folder.
`upload_drive_file_inline`	A small document (256 KB hard cap) straight from base64.
`update_drive_file`	Rename, move, or re-describe a document.
`delete_drive_file`	Delete it. Previews first unless `confirm: true`.

Why upload is two steps for an agent

MCP tool arguments are written by the model, so base64 content costs about 1.4 tokens per byte of file — a real document does not fit. create_drive_upload returns a signed upload_url and the exact headers to send; the agent PUTs the bytes with its own HTTP or shell, then calls register_drive_file. Keep upload_drive_file_inline for something genuinely small.

In short

The Drive is org-wide, so one document serves every project that references it.
Folders are paths on the documents, so they need no upkeep and cannot strand anything.
A document is referenced with @ and stored as [label](/__mention/file/<id>), which renders as a clickable chip on web and phone.
Documents are up to 100 MB, private, and served only through short-lived signed links.
Agents read the Drive under drive:read and write it under drive:write, with the same folders and the same links your team sees.