rdc-cli

# rdc-cli Skill ## Overview rdc-cli is a Unix-friendly command-line interface for RenderDoc GPU captures. It provides a daemon-backed architecture using JSON-RPC over TCP, a virtual filesystem (VFS) path namespace for navigating capture internals, and composable commands designed for shell pipelines, scripting, and CI assertions. Install: `pip install rdc-cli` (requires a local RenderDoc build with Python bindings). Check setup: `rdc doctor`. ## Core Workflow Follow this session lifecycle for any capture analysis task: 1. **Open** a capture: - Local: `rdc open path/to/capture.rdc` - Remote replay (Proxy): `rdc open capture.rdc --proxy host:port` - Split thin-client: `rdc open --connect host:port --token TOKEN` - Android device: `rdc open capture.rdc --android [--serial SERIAL]` 2. **Inspect** metadata: `rdc info`, `rdc stats`, `rdc events` 3. **Navigate** the VFS: `rdc ls /`, `rdc ls /textures`, `rdc cat /draws/0/pipeline/summary` 4. **Analyze** specifics: `rdc shaders`, `rdc pipeline`, `rdc resources`, `rdc bindings` 5. **Debug** shaders: `rdc debug pixel EID X Y`, `rdc debug vertex EID VTXID`, `rdc debug thread EID GX GY GZ` 6. **Export** data: `rdc texture ID -o out.png`, `rdc rt EID`, `rdc buffer ID -o buf.bin`, `rdc cbuffer EID --stage ps --binding 0`, `rdc log` 7. **Close** the session: `rdc close` ### Session Management - Default session name: `default` (or value of `$RDC_SESSION`). - Override per-command: `rdc --session myname open capture.rdc`. - ...