Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cyberwave.com/llms.txt

Use this file to discover all available pages before exploring further.

Cyberwave is built in the open with a small, responsive team and a growing community. This page is the single place to figure out where to go when you need help — whether you’re stuck on a quickstart, hit a bug, or want to talk to a human.

​
Where to get help

Discord community

The fastest place to ask a question, share what you’re building, or get unstuck. The team and other builders hang out here every day.

GitHub issues

Found a bug or want to request a feature? Open an issue on the relevant repo under the cyberwave-os organization (SDKs, CLIs, drivers, edge components, this docs site).

Contact us

For sales, partnerships, on-premises deployments, or anything that doesn’t belong in a public channel, reach out directly.

Status & changelog

Check what shipped recently and whether a recent change might explain what you’re seeing.
Not sure which channel to use? Default to Discord for questions and GitHub issues for reproducible bugs or feature requests.

​
Filing a good GitHub issue

A reproducible report gets fixed dramatically faster. When opening an issue on a cyberwave-os repo, please include:
  • What you ran: the command, code snippet, or UI action.
  • What you expected vs. what happened (include the full error or log output).
  • Environment: OS, Python / Node version, SDK or CLI version, and whether you’re on cloud or self-hosted.
  • Catalog item (if relevant): the asset, model, or driver slug — e.g. the-robot-studio/so101, unitree/go2.
  • A minimal reproduction if you can — even a 10-line script helps.
Pick the repo closest to where the issue lives (Python SDK, CLI, a specific edge driver, the docs, etc.). If you’re not sure, ask on Discord first and we’ll point you at the right place.

​
Catalog-item help (robots, models, datasets)

Most “how do I…” or “why isn’t this working” questions about a specific catalog item are answered on that item’s own page rather than here. Every catalog entry has its own setup guide, capabilities reference, and item-specific troubleshooting. Start there before opening a general issue:

Robot hardware

Per-robot setup, supported features, calibration tips, and known issues for each supported arm, mobile base, quadruped, and drone.

ML models

Per-model usage, supported inputs/outputs, training notes, and gotchas for each model in the catalog.

Asset catalog

How catalog assets, registry IDs, and slugs work — and how to upload your own.

Datasets & recordings

How datasets are generated from recordings, supported formats, and import/export options.
Rule of thumb: if your question starts with “for the SO-101…” / “for Go2…” / “for SmolVLA…”, the answer is most likely on that item’s page. This Support page covers cross-cutting questions about the platform itself.

​
FAQs

A growing list of frequently asked questions about the platform as a whole. For item-specific questions, see the catalog links above.

​
General

Placeholder. A short overview of the Cyberwave platform, what it’s for, and who it’s for.
Placeholder. Differences between Cyberwave’s digital twins and pure simulators, and when to use each.
Placeholder. How to evaluate Cyberwave entirely in simulation before connecting real devices. See Getting started.
Placeholder. Free tier scope, limits, and how to upgrade.

​
Accounts, workspaces & pricing

Placeholder. Workspaces, projects, and how isolation works across teams.
Placeholder. Inviting users, managing roles, and access control.
Placeholder. Pricing model, metered resources, and how to monitor usage.
Placeholder. Self-hosted and air-gapped deployment options.

​
Hardware compatibility

Placeholder. Current list of officially supported platforms. See Robotic hardware for per-item setup and troubleshooting.
Placeholder. Bringing your own hardware via custom hardware and writing compatible drivers.
Placeholder. Supported cameras, microphones, and other sensors.
Placeholder. ROS 2 interoperability today and roadmap.

​
SDKs & integrations

Placeholder. Overview of the Python SDK, C++ SDK, MCP server, and Claude Skill.
Placeholder. Setting up tokens. See Setup Cyberwave.
Placeholder. Connecting agentic IDEs through the MCP server.
Placeholder. Any HTTP client works; see the API reference.

​
Edge & deployment

Placeholder. Overview of the Edge runtime and where it runs.
Placeholder. From a Raspberry Pi and bench to industrial gateways.
Placeholder. Offline / intermittent connectivity behaviour and buffering.
Placeholder. See Writing compatible drivers.

​
ML models, workflows & datasets

Placeholder. Uploading and serving custom ML models.
Placeholder. Supported formats and runtimes (PyTorch, ONNX, etc.).
Placeholder. Authoring workflows and chaining nodes.
Placeholder. Generating datasets from recordings.

​
Teleoperation & streaming

Placeholder. Typical latency and how to optimize. See Live Teleoperation.
Placeholder. NAT traversal, TURN servers, and required ports.
Placeholder. Tested browsers and known limitations.

​
Security & data

Placeholder. Data residency, hosting regions, and retention.
Placeholder. Encryption in transit and at rest.
Placeholder. Roles, sharing, and access control.
Placeholder. Current and planned certifications.

​
Still stuck?

If none of the above unblocks you:
  1. Search the cyberwave-os GitHub org for an existing issue.
  2. Ask in Discord — usually the fastest path to an answer.
  3. Open a new GitHub issue on the relevant repo with the details from the filing a good issue checklist above.
  4. For private or commercial questions, contact us directly.