Skip to content
  1. GUIDES

Local Data and Files

LOPs writes local files to manage the Python environment, store provider settings, run sidecar services, and optionally log API traces.

Storage locations
Install config
dotLOPs config in your app-data folder
UV binary
dotLOPs uv folder in app-data / Application Support
Python environment
The folder you chose on the Environment page
Project config
.lops/ next to the .toe (when using folder-tier config)
SideCar services
sidecars/ under the LOPs base folder
  • Python environment and installed packages.
  • ChatTD provider, model, and endpoint settings.
  • MCP client/server configs (session, project, folder, or user tier).
  • Agent profiles and skills.
  • SideCar environments, server files, and ports.
  • Per-operator outputs — generated images, exports, ratings, file outputs.
  • API traces, when enabled.

ChatTD stores keys locally in the project COMP. Some operators may also store provider keys in dotLOPs or environment-adjacent JSON files. If you are sharing a project, check provider settings and operator configs before sending the .toe or project folder.

Traces are written to LOP_history/traces/ under the LOPs Python environment folder. LOPs does not upload traces anywhere.

Your local model server (LM Studio, Ollama, etc.) may also keep its own logs — those are separate from LOPs traces.

Before sending a project to someone else:

  1. Back up or stub operators you do not want to share internals for.
  2. Check for operator output folders that should be excluded.
  3. Review API key storage and provider settings.
  4. Review trace files if including the environment folder.
  5. The recipient should run the Environment page on their own machine — do not expect the original venv path to work.

Deleting the TouchDesigner project does not remove the LOPs Python environment, SideCar environments, UV binary, or app-data config. Remove those folders manually for a full cleanup.