Good questions.
Useful answers.

Start with an expressive companion, differential-drive rover, robot arm, walking robot layout, vacuum concept or camera rig. Every template is editable, and an empty workbench lets you assemble your own design from the component library. Explore the robot collection.

You can use the website directly in a modern browser. Interactive 3D needs WebGL, and the code and simulation engines use browser workers and WebAssembly. A larger screen and a mouse make detailed assembly easier. Installation as a web app is optional; see the installation guide.

Explore robot presets, documentation and the workbench without signing in. Google sign-in creates a free profile for account settings and support requests. Your robot projects stay in this browser. Export JSON backups to keep or move them.

Google sign-in needs the operator's Google OAuth credentials and callback configuration. It is not ready until those have been supplied and configured. The account page shows the available sign-in options; a Google AI API key does not configure Google account login.

Mechanical attachment and electrical wiring are separate. Assembly snapping aligns supported generic mounting points and attaches a child part. In Wiring, drag a named pin toward another pin to preview and snap an electrical endpoint. Electrical parts automatically appear as wiring cards. Read about mounting or visual wiring.

Right-click the object and choose the related model-replacement action. Review which connections can be retained, then apply the change. The same menu provides relevant actions such as inspect, mount, detach, duplicate, group, hide, lock and delete. Locked parts need to be unlocked before editing. Undo lets you review and reverse project edits.

Yes. Save an assembly group as a reusable module, then add it from the Modules library. Module files include selected parts, their internal attachments and internal wires. External connections and project code are separate. Export your module JSON to move it to another browser or keep a backup.

The models are generic and uncalibrated. Supported differential-drive behavior couples battery, motor and traction estimates with rigid-body contact. Arms, legs and pan/tilt rigs use kinematic previews; joint forces, dynamic balance and moving-link contacts are not solved. Manufacturer fit, electrical correctness and hardware safety cannot be certified by a clean preview. Review the coverage table.

The legged presets demonstrate independently commanded joints in place. They do not have a dynamic gait, footfall or balance solver. Arm presets similarly demonstrate link motion without grasping or solved actuator torque. Each robot's landing page states the behavior currently supported.

The current runtime executes high-level JavaScript against Robot Forge's virtual device API in a bounded QuickJS worker. It is not an instruction-set or firmware emulator. ESP32 labels describe the selected generic board layout and supported pin aliases; they do not make an Arduino sketch or ESP-IDF binary executable here.

Open the template's included starter code, inspect wiring diagnostics, and confirm power, ground and required control paths. Use Run, then check the console and live telemetry. Low voltage, missing connections, stopped commands and unsupported motion can explain a stationary design. The documentation explains the supported behavior for each robot family.

Choose a supported cloud provider or local Ollama, then discover models or enter an exact model ID. The selected model must support the required action format and any optional image input. Your provider account controls access, usage charges and limits. The offline sensor fixture is available without a model request. Read the AI setup guide.

Keys entered in the dedicated AI key field stay in the current tab's memory and are excluded from project, module, report and trace exports. Cloud requests necessarily send that key through the site's server to the selected provider. Keep credentials out of code, names and objectives, because those fields can be exported. See the privacy policy.

Robot projects, modules and workbench preferences remain in this browser's local storage. An application account is separate and does not automatically synchronize robot files. Export project and module JSON for a portable backup; clearing site data or moving to a different browser can remove access to local work.

When you submit the website's contact form, your supplied contact details and message are sent to the site's backend for storage and review by authorized project administrators. This is separate from browser-local robot projects. Do not include provider keys or other secrets in a support message. The contact page shows submission status, and Privacy describes the data handling.

A connection is required to load the simulator and make cloud AI or account requests. The PWA provides an informational offline fallback and limited asset caching; it does not promise a fully cached simulator. Browser-local project storage is separate from that cache. Export important work before clearing data, uninstalling with data removal or switching browsers.