Skip to main content

Integrations and Media

Telemus AI brings supported files, maps, media, models and remote desktops into the workspace. Availability depends on the installed release, configured accounts, platform permissions and network policy.

Spatial File Browser​

Open Files to browse configured sources. Supported integrations include Google Drive, Dropbox, OneDrive, SharePoint and selected network-storage protocols. A configured source can still be unavailable on the current host.

Connect accounts through the supported sign-in flow. Do not paste access or refresh tokens into chat. Cloud mutations require the relevant provider capability and review. Some providers allow duplicate display names; that is separate from replacing an existing file.

Browser builds support file picking where the browser permits it, with app-managed local storage where available. Browser file access does not grant access to arbitrary files on your computer. Native SMB, NFS, FTP, SFTP and WebDAV access is unavailable in the standalone browser build.

Connected Files in Web and the terminal​

Open Connected Files in Command Center or use /files in the terminal. These views use the connected app's providers; they are separate from the Web workspace's dashboard-local Files pane.

  1. Choose a provider, root and folder.
  2. Use Next, Back, and Reset / refresh to browse.
  3. Select a source file before requesting an upload.
  4. Review requested changes in Web Approvals or terminal /approvals.
  5. Refresh the listing after an approved change.

Available actions depend on the provider: New folder, Rename, Delete, and Upload selected source may be unavailable. A truncated listing is not a complete folder. Pending confirmation is not a completed change.

Reviewed uploads are limited to 4 MiB and do not overwrite an existing destination. A changed source or unsupported source/destination operation fails rather than silently changing the reviewed upload. If a request times out, inspect Approvals before trying another mutation. Platform validation and provider support vary; this workflow is not a promise of complete cross-provider support.

/files providers
/files open 1
/files next
/files back
/files reset
/files source 2
/files clear-source
/files duplicate-names on
/files duplicate-names off
/files mkdir New folder
/files upload Destination name.txt
/files rename 2 New name.txt
/files delete 2

Row numbers refer to the current listing. File preview remains a supported native spatial Files action; these Web and terminal controls manage listings and changes.

Documents and local media​

  • PDFs: Supported native builds display PDF pages in the room. Web 3D offers a link card or a browser-local download where available. A link card or accepted viewer launch does not prove that a document opened.
  • Text extraction: read_pdf can extract supported document text. Scanned pages require an available OCR provider. Missing OCR or unsupported files report a limitation rather than fabricated text.
  • Images and video: Open supported files as workspace surfaces. Video status distinguishes a request from actual playback. Codec support, browser gestures, CORS and network conditions can prevent playback.
  • Audio: WAV and MP3 are supported where their decoders are available. Other formats depend on the device. Pause, restart and stop controls vary by player; a file can remain available for restart after stopping.
  • Archives: Supported archive types can show a contents listing. Corrupt or protected archives may provide only metadata and an external-open option.
  • Desktop drag-and-drop: Drop supported documents, images, video, audio, models, archives or text/code files into the workspace.
  • Generated media: generate_image can create an image using a configured provider, subject to its permissions and cost.

Local previews reject unsupported or sensitive paths. These checks are not a security scan of file contents. Open only files you trust. Windows remote-file materialization and other platform-specific operations can remain unavailable.

Agent write_file and search_replace actions use the permitted workspace or host scope. An unscoped host configuration can allow writes under the account's home directory. Check the active scope and approval policy before requesting edits.

Browser-local downloads​

For an eligible local PDF, open its card and choose Download PDF. Cancel dismisses the offer; an expired offer must be requested again. Supported files must be readable, nonempty PDFs no larger than 64 MiB. The browser controls whether saving succeeds. A download offer is not a PDF viewer or proof of saving.

Browser-local video is also limited to 64 MiB and still depends on browser codec and gesture support. A second tab or failed local-storage state can make file operations unavailable. Do not treat a cached view as a durable backup.

Models​

Model Center supports importing available GLB, glTF and .vraimesh assets into a model library. Related textures and buffers must be available where the chosen format needs them. Use import_model or show_model_center for supported workflows. Installed releases may also offer reviewed uploads in 3D Assets.

Registered models can be listed, spawned and manipulated using scene controls. Materials and animation depend on the asset and renderer. Full PBR, transparency and custom-sampler behavior are not guaranteed; preview appearance may differ between the browser viewer and native scene.

Browser viewing and automation​

Passive web panels and active browser_* tools are different capabilities. On a compatible desktop host, active tools can navigate and interact with a configured browser. Android and iOS integrations are limited to supported app-owned browser controls; iOS does not control Mobile Safari or other apps.

Standalone Web automation is limited to supported app-owned, same-origin content. Full remote automation requires a configured authenticated companion. A browser screenshot from a limited target may be a clearly labeled summary rather than page pixels. iOS local automation does not support JavaScript dialogs or scripts registered for future page loads.

Ordinary browser tools do not provide an isolated private operator browser. Do not assume they are prevented from reaching private pages accessible to the configured browser account.

Maps and remote desktop​

Tabletop maps and geocoding help place geographic references in your workspace. Map views retain the required OpenStreetMap attribution.

RDP viewing is available on compatible Linux, Windows and macOS desktop builds. It is unavailable on Android/Quest, iOS and standalone Web. A supported build must include its remote-desktop capability; installing a dependency does not upgrade an existing app binary.

The viewer is view-only by default. Supported Linux builds offer local input: point inside the viewer and press Ctrl+Shift+F8. Press Escape, click outside, or use the toolbar to release input. X ends the session. Focus loss or reconnect releases input; it is never restored automatically. Clipboard, IME, file exchange and horizontal scrolling are not included. Input on other targets remains unavailable. rdp_status reports the current capability and mode.

Web, terminal and assistant controls cannot enable remote-desktop input. A network failure may prevent releases from reaching the remote machine.