Working with Baby Whale

Files & workspaces

Everything Baby Whale touches lives in a workspace folder you chose — on your disk, in folders you can open, read, move, and delete.

Workspaces

A workspace is a local folder bound to your sessions. The sidebar groups sessions under their workspace; picking a workspace at "New Session" time decides where that session's files will live. Use one workspace per project — it keeps deliverables where you'll look for them.

Uploading files

Attach files directly to a chat message — spreadsheets, CSVs, and Word documents are first-class:

Format	Read with	What Baby Whale gets
.xlsx	`xlsx_read`	Sheets, cells, formulas, and formatting structure.
.csv	`csv_read`	Rows, columns, and value types.
.docx	`docx_text`	Document text and structure.

The upload lands in the session's uploads/ folder. Analysis happens against the real file — no lossy paste, no transcription step.

Session folders

session folder

quarterly-review/
├── uploads/        # files you attached
├── scripts/        # code Baby Whale wrote and ran
└── deliverables/   # finished files, ready to open

Nothing in these folders is special or locked — they're ordinary files. Copy them into your drive, commit them, or archive the folder when the session is done.

Privacy

Baby Whale is local-first by architecture, not by promise:

There is no Baby Whale cloud — no account, no sync, no telemetry pipeline, nothing that could retain your files.
The only network calls are to the model provider you configured, the one-time runtime download, and update checks — same as any install you'd run yourself.
Delete a session folder and the data is gone; there is no server-side copy to worry about.

ⓘ

Sharing a machine? Workspaces are plain folders with standard file permissions. Whoever can read the folder can read the session — choose the location accordingly.