explorer-remote-proxy

name	explorer-remote-proxy
license	Apache-2.0
version	1.0.0
description	Run the locally-built Explorer UI against a REMOTE, fully-hosted USD Search instance by proxying every API call through the local gateway. No local deepsearch-api / OpenSearch / SigLIP2 / Asset Graph Service — only the Explorer + gateway run locally, so search, thumbnails, dependency graphs, and downloads all work exactly as on the hosted instance (which already has a populated index + AGS + storage). Use when: you want to test/demo the local Explorer with WORKING dependency graphs and downloads but don't want to (or can't) build a local index + Asset Graph Service. Default target is the public staging instance (api.staging.deepsearch-horde.nvidia.com).
triggers	["explorer against remote","proxy explorer to staging","test the ui with dependencies","show dependency graphs in the ui","run the explorer against the hosted instance","staging hybrid","reuse the staging setup"]
allowed-tools	AskUserQuestion, Bash, Read, Edit, Write

/explorer-remote-proxy — local Explorer, remote backend

Stand up ONLY the redesigned Explorer + gateway locally and proxy the entire API surface (, , , , , , , , ) to a hosted USD Search instance. The hosted instance already has a populated index, a populated Asset Graph Service, and storage access, so the features that need a backend — — work with zero local infra.