What problem does it solve? Adapting Physical Intelligence's OpenPI vision-language-action models (pi0, pi0-fast, pi0.5) to custom robot datasets involves complex setup across JAX and PyTorch backends, checkpoint conversion, normalization statistics, and low-latency policy serving, all of which are error-prone without a guided workflow. ## Core Features & Use Cases - JAX and PyTorch Fine-Tuning: Config-driven training on LeRobot or RLDS datasets with norm stats computation, FSDP sharding, and multi-GPU DDP support. - Checkpoint Conversion: Convert JAX checkpoints to PyTorch format with required transformers patches for deployment-friendly inference. - WebSocket Policy Serving: Run inference servers for ALOHA, DROID, and LIBERO environments with a lightweight remote client for robot integration. - Use Case: A robotics researcher fine-tunes pi0.5 on a custom DROID dataset, computes normalization statistics, trains on an A100 cluster, then serves the checkpoint over WebSocket so a remote robot client can request action chunks in real time. ## Quick Start Ask the AI to clone the OpenPI repository, install the workspace with uv, and start a pretrained DROID policy server, then connect a WebSocket client to run inference.