AI agents

Give your agent a good starting point.

Use official sources, describe the actual setup, and keep control of any action that could move the robot.

Copy Sourccey context

Paste this into your coding agent before describing your task. It provides context; it does not install a skill or grant access to your robot.

Agent context · plain text

You are assisting with Vulcan Robotics Sourccey.
Official documentation: https://vulcanrobotics.ai/docs
Developer setup: https://vulcanrobotics.ai/docs/lerobot
Source: https://github.com/vulcan-forge/lerobot-vulcan

Read the relevant official docs and inspect the actual repository before proposing commands.
Confirm the user's hardware revision, software commit/version, OS, controller computer, robot computer, and intended task.
Do not invent CLI flags, hardware specifications, APIs, joint IDs, pinouts, or capabilities.
Label every command with its execution computer and shell; explain placeholders and expected results.
Do not initiate physical robot movement without explicit human approval and supervision.
Confirm the stopping procedure for the actual hardware revision before any motion.
Give a test and rollback procedure. Report discrepancies between docs and code instead of guessing.
Existing website commands are pending a pinned-source and physical-hardware walkthrough; do not treat their presence as proof of safety or compatibility.

Describe your task and setup

State the intended result: diagnose a connection, inspect data, or prepare a training configuration.
Include your robot revision, software commit or version, and operating system.
Identify which terminal is on the controller and which is on the robot.
Include exact errors with passwords, tokens, and private information removed.
Ask the agent to explain its proposed commands before you choose to execute them.

Read without a browser

The developer subguides have raw Markdown generated from the same content used by the website. The consolidated export contains those six subguides and the agent context; it is not a complete export of every docs page.

Documentation index: a compact list of available guides.
Consolidated developer guides: plain-text Markdown.
Teleoperation Markdown: an individual guide; replace the final segment with record, replay, train, rollout, or troubleshooting.

Keep hardware actions supervised

Approval is specific to the action

Reading documentation or preparing code does not authorize movement. Review the proposed action, confirm stopping behavior for your revision, and explicitly approve and supervise any physical test.

Start with non-motion diagnostics when possible. If code and documentation disagree, record the discrepancy and check the source before proceeding.