Live Files and Viewers

Browse approved app sandbox roots and inspect captured artifacts through bounded, host-owned viewers in the local player.

The local player uses the host’s file-visualization service for connected app sandboxes and persisted artifact snapshots. Browser code receives bounded content and typed viewer data, never an unrestricted host filesystem path.

Browse a connected app

When the selected live session exposes the files.* suite, use the Files view to browse only the roots approved by the app. Read access can include directory listing, text or binary download, checksum, and format-aware preview. Push, copy, move, and delete remain separate write or critical operations governed by the SDK policy.

Captured artifacts

Artifacts stored with a session remain available after disconnect. The host resolves persisted artifact paths beneath the captured snapshot directory and applies bounded reads before returning viewer data.

Built-in viewers

Depending on the installed host version, the player can render:

  • structured JSON and XML;
  • binary or XML property lists;
  • CSV tables and Markdown;
  • source code and plain text;
  • images, PDFs, audio, and video;
  • SQLite schema and read-only query results;
  • GLB, glTF, OBJ, and STL assets.

Unknown or oversized files fall back to metadata and explicit download instead of being interpreted speculatively.

SQLite safeguards

SQLite inspection is read-only. The local player accepts bounded SELECT, WITH, PRAGMA, or EXPLAIN queries and does not open a database directly in browser code. Export a working copy before using an external application that may mutate the file.

CLI access

Agents should discover the file or artifact tool first, then use the relevant ansight app call, ansight session artifacts, or export command. Avoid copying secrets or unrelated app data into a prompt merely because a file is available.