Drift CLI provides intelligent debugging capabilities that go far beyond traditional error messages. Using AI-powered analysis, Drift helps you understand what’s wrong, why it’s happening, and how to fix it — all through natural language conversation.
Drift’s debugging combines system analysis, log parsing, and AI reasoning to provide actionable solutions to common and complex robotics issues.
Analyzing camera issue...Found the problem:- The camera plugin is loaded but the image topic is not being published- The camera_info_topic parameter is set incorrectly in your URDF- Expected: /camera/camera_info- Found: /camera_infoFix: Update the camera plugin configuration in your robot URDF.Should I fix this for you?
Root cause analysis
Drift identifies the underlying issue, not just symptoms.
Context-aware solutions
Recommendations are specific to your robot and configuration.
Automatic fixes
Drift can often fix issues automatically with your permission.
Learning system
Drift learns from common issues to provide better assistance.
drift> why won't my robot move?drift> what's causing this segmentation fault?drift> why is Gazebo running so slow?drift> why can't I see my robot in RViz?drift> what's wrong with my controller configuration?
Each query triggers intelligent analysis of your specific situation.
Be as specific as possible in your debugging questions. Include symptoms, recent changes, or error messages you’ve seen.
drift> rebuild my workspace[Build fails with compiler errors]Build failed: missing dependency 'gazebo_ros_control'I can fix this by:1. Adding the dependency to your package.xml2. Installing the missing packageShould I proceed with the fix?
drift> launch my robot[Controller manager fails to start]Error detected: controller_manager failed to initializeAnalyzing logs...Issue: The controller configuration file is missing required parameters.Specifically, 'update_rate' is not defined.I can generate a complete controller config with recommended settings.Would you like me to do that?
drift> why did Gazebo crash?Checking logs...Gazebo crashed due to:- Invalid SDF in world file at line 45- The <physics> tag is not properly closedLocation: ~/.gazebo/worlds/my_world.world:45I can validate and fix your world file. Proceed?
While Drift can fix many errors automatically, always review changes to understand what was modified, especially in production code.
drift> launch my robot[Launch fails due to timing issue]Launch failed, but this looks like a timing issue.Retrying with proper node sequencing...[Successful launch]
drift> my robot isn't movingLet me check several things:✓ Robot model loaded correctly✓ Controllers are running✗ No cmd_vel messages being publishedThe issue is in your navigation stack.Checking navigation configuration...✗ Navigation nodes are not runningRoot cause: Navigation launch file wasn't included.Should I add it to your main launch file?
drift> debug my custom plugin errorI see a custom Gazebo plugin is failing to load.Here's what I found:1. The plugin library exists at the expected path2. Symbol loading is failingThis is likely due to:- ABI compatibility issues- Missing library dependenciesTo debug further, try:1. Check plugin dependencies: ldd /path/to/plugin.so2. Verify Gazebo version compatibility3. Review plugin code for API changesWould you like me to check the plugin dependencies?
drift> add a lidar sensor to my robot and rebuilddrift> launch my robotdrift> why isn't the lidar data appearing in RViz?[Drift analyzes topic connections, frame transforms, and RViz config]Found two issues:1. The lidar frame_id doesn't match your URDF2. RViz is not configured to display LaserScan messagesFixing both now...
drift> my robot arm isn't responding to commands[Drift checks controller manager, joint states, command topics]Diagnosis:- Controller is loaded but not started- Missing controller startup in launch fileAdding controller spawning to launch file...Restarting controller manager...Try sending commands now.
drift> why isn't my robot receiving velocity commands?[Drift checks topic connections]Analysis:- /cmd_vel topic exists- Publisher is active (navigation node)- Subscriber is active (controller)- But namespaces don't match!Publisher: /robot1/cmd_velSubscriber: /cmd_velAdding topic remapping to fix namespace mismatch...
drift> debug transform issues[Drift analyzes TF tree]Transform problems found:1. Missing transform between 'base_link' and 'camera_link'2. TF publisher not runningThis is usually caused by:- Missing robot_state_publisher- Incomplete URDF joint definitionsChecking your URDF...Found: camera_link is not connected via jointsShould I add the missing joint definition?
Transform issues are among the most common problems in robotics. Drift’s TF debugging can save hours of manual investigation.
drift> launch my robot[Drift validates before launching]Validation checks:✓ URDF syntax valid✓ All mesh files exist✓ Controller config complete⚠ Warning: Camera frame rate (100Hz) may cause performance issuesRecommended: Reduce to 30Hz for better performance.Continue with launch anyway? (y/n)
drift> add a lidar sensor to my robot and rebuild[Drift notices potential issue]Warning: Your robot now has 3 high-frequency sensors.This may impact real-time performance.Consider:- Reducing sensor update rates- Using selective sensor activation- Increasing physics time step
drift> create a mobile robot with cameraRobot created successfully!Tip: For optimal camera performance, consider:- Setting update_rate to 30Hz (default is 60Hz)- Using compressed_image_transport for network efficiency- Adding proper lighting in your world file
drift> why won't my robot move?[Drift identifies controller issue]drift> fix the controller configuration[Drift fixes it]drift> now why won't it move?[Drift finds the next issue: missing commands]
