Status
This page is a stub and will be expanded with complete examples.Current Coverage
- The C++ SDK now mirrors the regenerated REST surface for canonical environment export downloads, scene composed-schema fetches, environment previews, asset universal-schema rebuilds, workflow slug lookups, and twin universal-schema helpers.
- Twin latest-frame calls now follow Python-style source resolution: simulation defaults to
source_type=sim, while live mode omits the query unless the caller explicitly requests a compatible frame source. Client::twin()now covers the main quickstart path for fetching by twin UUID or resolving an asset registry id / alias into a reusable twin, and it can auto-bootstrap a default workspace/project/environment context when none is configured yet.- Regular C++
Twinhandles now expose the core capability helpers directly for locomotion, gripper, flight, and streaming workflows, so the main client and manager paths no longer stop at a base-only twin surface. Client::affect()now matches Python’s runtime-mode defaults end to end: simulation usessimfor REST/frame reads,sim_telefor control MQTT writes, live modes reset the defaultsource_typeback toedge, and switching modes disconnects the active MQTT client so it can reconnect with fresh runtime settings.AssetManager::upload_glb()now mirrors Python’s large-file behavior by switching oversized GLBs to the attachment signed-upload flow and retrying there automatically after payload-too-large direct uploads.- MQTT config supports topic prefixes, MQTT v5 selection, runtime-mode-aware client IDs, client-side event publishing helpers, and workflow-run status subscriptions on
cyberwave/workflow-run/{uuid}/status. - A first
DataBusmilestone is now available with canonical wire-format helpers, validated data-key builders, a filesystem backend, and JSON / bytes / ndarray roundtrips for local development. - Worker parity now includes a hook-registration surface plus a first manifest schema / dispatch-mode helper, ready for a later runtime layer.