Project memory for scientific workflows.
Scientific work rarely fits inside one chat. Protocol drafts, audit certificates, uploaded papers, data tables, generated plots, and notes need stable places to live. Workspace Files gives Vicena a durable project surface: save the output of one session, hand it to another tool or agent, and build the next modeling, audit, or optimization step from normal paths.
The file is the durable object. Conversations supply context; tools write outputs, later workflows read those outputs, and the project advances without copy-paste.
Workspace Files
project continuity
work session
Generate evidence.
Literature, simulation, plots, and audit outputs become project files.
project folder
/Projects/Gold Nanoparticles
next workflow
Continue from state.
- read results
- change parameters
- run next model
- write audit
Workspace Files turns separate chats, tools, and computer runs into one project memory: write results once, then pass them into the next scientific workflow by path.
Collect
Keep uploaded papers, PDFs, images, CSVs, and notes in named project folders instead of scattering them across chats.
Produce
Save protocol drafts, audit certificates, data tables, plots, and code snippets as durable outputs with stable paths.
Reuse
Let later chats read the same files, compare versions, continue unfinished work, and build from prior results.
Design boundary
Files are durable records. Conversations are context. The computer is execution.
Normal file paths
A workspace file is addressed by a forward-slash path such as /Protocol Audits/fischer-esterification.md. The path and extension determine how the interface opens and renders it.
Separate from conversations
Chats can reference files, but conversations do not own them. A protocol, dataset, model output, or audit certificate can become input to another session without copying the entire conversation.
Separate from the computer
Workspace Files are durable research records. Scientific Simulations notebooks and the Jupyter filesystem are execution volumes. Direct copying between them is not available yet, so the agent should not claim a transfer happened.
Agent operations
What the agent can do with files
The agent should behave like a careful research assistant working in a project folder: read before editing, create folders deliberately, keep paths explicit, and avoid destructive operations unless asked.
list
Inspect folders and discover prior work by path.
read
Open text files directly; binary files return metadata and preview/download routes.
write
Create Markdown notes, protocol drafts, audit certificates, JSON, CSV, or other files.
patch
Edit text files by replacing sections or lines instead of rewriting everything.
organize
Create folders, move files, rename files, and delete only on explicit request.
upload
Store PDFs, images, CSVs, and other user files in the workspace inbox or selected folder.
Example requests