Native file service

Local asset folders

Files 0.1.0 supplies Windows applications with shared asset catalogues and selected project folders. Select Files in the app's Sidecars, then create a fresh Compile and Windows package. Rebuild/restart the cApp owner first when installing this update. Files has no floating window: the application provides its own folder controls.

The default pool is the current user's cApp/assets, with 3d and audio subfolders. Open project folder uses a native folder picker. The last project and shared location are saved on disk. Missing remembered folders are reported; they are not silently replaced with an empty library. Browser storage is a cache.

The installed API is window.capp.files, with protocol: "capp.files.v1" and an asynchronous request(payload) method. It returns an operation result or rejects with a visible error; applications must wait for acknowledgement before reporting that a save succeeded. It is available only when Files is selected in a Windows package. Ordinary browser previews and Android do not expose this native API.

const files = window.capp?.files;
if (files?.protocol !== 'capp.files.v1') throw new Error('Files is unavailable');
const shared = await files.request({service: 'project', route: 'local/status'});
const selected = await files.request({
  service: 'project', route: 'projects/open', method: 'POST', value: {}
});
if (!selected.cancelled) console.log(selected.project.name);

Requests select a bounded model, audio or project service and a declared route. They do not accept shell commands, executable paths or arbitrary filesystem roots. Folder selection is native-owned. Project handles are scoped to remembered folder grants; sharing an app tab does not transfer filesystem authority.

The catalogue adapters preserve Lab IDs, editable recipes, reference images, immutable revisions, conflict checks and recovery. Foundry owns project assignments, assembly validation and publication. Copying a revision does not spawn an object or automatically publish it into a game. Existing optional HTTPS/loopback connections remain a separate remote transport.

Files packages a pinned private Python interpreter and the storage helpers; it requires neither Local AI nor a system Python installation. Operations run through owned stdin/stdout with no listening port. Each app can work independently; the cApp development owner does not need to remain open. The build hook verifies the interpreter archive and packaged source closure and runs an import probe on Windows. Source, temporary-disk and browser-shim checks do not certify installed Windows folder dialogs, packaging or performance. That acceptance remains pending.

Configuration reference

These are the selected package's configuration fields. String credential values and installation-specific defaults are never published here. A field's presence does not bypass its runtime policy.