Skip to main content

​
Overview

User files are everything you’ve given Dexter to look at — data exports, work instructions, drawings, images, whatever the task needed. Every file you attach is kept in the Factory and managed in the Uploaded files folder under Data → Files, so Dexter can open it again in a later conversation without you re-uploading it. Your uploads live in this data library — not the Knowledge Base, which holds Dexter’s memory rather than the file library.

​
Adding Files

Three ways to get a file in:
  • Drag and drop onto the chat — you can drop multiple files or a whole folder at once.
  • Upload files — in the + menu of the message composer.
  • The Data page — open the Files tab and click Upload files (or drag and drop anywhere on the page).
However a file arrives, it lands in the same place: the factory’s file store, listed in the Uploaded files folder of the Files tab on the Data page. Dexter can read it immediately. What happens next depends on where you uploaded and the response mode:
  • In chat, in Max or Ultra mode, Dexter runs an exploratory analysis on fresh data before other work. In Turbo and Fast, it works from the file directly.
  • On the Data page, an Analyze your new data? prompt appears once the upload finishes. Click Analyze it to ask Dexter for an exploratory analysis, or Not now to skip it.

​
Supported Formats

Individual files can be up to 2 GB.

​
How Dexter Uses Your Files

  • Reads them directly, in the conversation you uploaded them in and in every future one — reference a file by naming it: “Look at the throughput export I attached last week.”
  • Profiles data files (CSV, Excel) column by column and confirms its reading with you — ambiguous codes, unlabeled units — before treating anything as ground truth.
  • Reads documents (PDF, Word, PowerPoint), pulling out their text and tables.
  • Analyzes CAD files through the CAD analysis tooling — geometry, part counts, dimensions.
  • Writes a memory entry. When Dexter builds a working understanding of a data source, that understanding lands in the Data sources area of your knowledge base — schema, what the codes mean, common pitfalls — so the next conversation doesn’t start from zero.
Upload a production log once and every future conversation can use it. The file carries the raw data; the knowledge base carries what Dexter learned about how to read it.

​
Persistence and Cleanup

  • Files persist for the life of the factory and are available to every conversation in it.
  • Files are scoped to the factory — a file uploaded in one factory is not visible from another.
  • Delete a file from its row menu in Data → Files → Uploaded files. The same menu offers download; click the file itself to preview it. Once deleted, Dexter can no longer read it in new conversations.
  • Sharing a factory doesn’t hand over your uploaded files. Whoever you share with gets a copy of the factory, but not your raw uploads. Anything from those files that already made it into a built artifact — a simulation model, a BOM — does travel with that artifact.
Uploaded files do not travel with a factory export. If you import a factory, re-upload the source files in the new copy.
Deleting a file does not delete what Dexter learned about it — the Data sources entry stays in the knowledge base until you prune it. Ask Dexter to clean up the entry as part of the same request.

​
User Files vs. Reports

  • User files are files you attach for Dexter to read.
  • Reports are files Dexter generates for you to download and share.
Both are visible in the Files tab of the Data page — uploads in the Uploaded files folder, generated deliverables in the Reports folder.