Lavern · Explore

Cowork folder mode

Deliverables don't have to leave the user's machine. Cowork mode connects the dashboard to a local folder via the browser's File System Access API, so Lavern can read source documents and write its output back without an upload round-trip.

What it changes

• Inputs stay local. The browser hands Lavern a handle, not bytes. Source documents are read from disk on demand.
• Outputs land beside them. Final deliverables, audit bundle, and derivatives write back into the same folder, with the user picking exactly which files are in scope.
• Non-destructive by default. The user keeps full control over what gets touched — selection is explicit and revocable.

Surface

CoworkFolderPanel.tsx	Connected-folder UI inside the QuickStart card: name, file list with checkboxes, disconnect button
useCoworkFolder.ts	Hook around the File System Access API — pick directory, list files, request permission, write artefacts
coworkStore.ts	Store of files in scope and their selection state
file-system-access.d.ts	TypeScript types for the FS Access API where the browser typings lag

Where it shows up

Two places: the landing QuickStart flow (point at a folder to start an engagement against its contents) and the Delivery view's DownloadPanel (save the final bundle straight back into the connected folder, not into Downloads).

Browser caveat

The File System Access API is Chromium-only at the time of writing. The dashboard falls back to traditional upload/download on browsers that don't expose it — the cowork panel simply doesn't appear.