Chats and document transformations

The Chats and Documents sections use the configured AI endpoint but serve different workflows. Chats are conversations with optional file context; Documents keeps a durable project and version history for text transformations.

Chats

Start a chat from the activity rail or from selected files in the browser. A conversation can include files from the active, unambiguous database root. Attached images, archive pages, video sprites, and supported documents expose a preview so you can verify the context before sending it.

Chats can be docked in their section or opened as a movable, resizable floating window while you browse. Saved conversations keep their existing session ID and autosave subsequent exchanges. A brand-new unsaved conversation is not silently turned into a saved one; save it explicitly when you want it in the session list.

If an attached file disappears, Tessera marks it unavailable rather than silently substituting a file with the same name from another root.

Transformation projects

Choose a supported document or text file in Files and start a transformation. The Documents section opens a project workspace containing:

  • the original source;
  • an instruction composer;
  • a project list and version tree;
  • the selected result editor;
  • a project chat for follow-up changes.

The project, its jobs, chat messages, and derived versions are persistent. A follow-up transformation or manual edit creates a child version, so alternate branches remain visible. Panel widths are resizable and remembered locally.

Finished results can be edited, exported, renamed, or deleted. Deleting one derived version keeps its descendants by reconnecting them to the deleted version's parent. Deleting the project is a separate action that removes the whole project history.

Running versions remain read-only. Failed transformations can be resumed when completed chunks are available, or restarted as a fresh run.

The standalone file editor described in Browsing and tagging is intentionally separate: editing an ordinary file does not create a transformation project.