Compare two forks
Compare features, settings, and device support.
Your device
Forks
Choose at least two forks.
Your car
Answers cover reviewed versions. Open details for devices, car requirements and version limits.
Separates steering assistance from speed control, so you can manage the accelerator and brake. Engagement and pedal settings vary by fork and car.
Useful when you want help staying in the lane without handing over every speed decision.
Example: you control speed through a construction zone while the software continues helping with steering.
Driving profiles such as Relaxed, Standard or Aggressive change following and speed-control behavior. Some versions offer direct distance controls instead. Names and options vary.
The same following distance can feel too relaxed to one driver and too busy to another.
Example: choose a calmer response for traffic or a more responsive one on an open highway.
Adds controls that can lower the assisted speed when the road bends.
A set cruise speed can feel too fast when a sharp curve arrives.
Example: the target speed drops before a freeway ramp instead of waiting for you to brake.
Adds controls that can show, warn about, or respond to a detected speed limit.
It can reduce the need to keep changing the set speed as limits change.
Example: the display warns you when a road changes from 55 to 45 miles per hour.
Switches between standard and Experimental speed control using project-specific conditions. Requires software control of speed on a supported car.
Reduces manual mode changes; each fork uses different triggers and settings.
Example: switch modes when the configured speed or predicted slowdown conditions are met.
Adds controls for when a signaled lane change starts and how much confirmation it needs.
Drivers differ on whether they want a steering nudge, a short delay, or more automatic behavior.
Example: signal, check that the lane is clear, and let the configured lane-change action begin.
Adds a small steering correction toward the detected center of the lane when the lane lines are clear.
It can give the car a more centered feel without replacing the driving model's planned path.
Example: the car adds a gentle correction when its planned path drifts from the center of clear lane lines.
Adds controls for selecting or downloading the model that plans the driving path.
Different project-provided models can feel different, but a different model is not a promise of safer or self-driving behavior.
Example: try another project-provided model, then return to the previous one if you prefer its behavior.
Adds controls for downloaded map regions, road names, or an on-screen map view.
Road context can make the display more useful and can support some project-specific driving helpers.
Example: download a region before a trip or show the current road name while driving.
Adds route guidance that can tell the driving model about an upcoming turn or lower speed before a sharp maneuver.
Route-aware controls can help prepare for a selected turn or exit; a turn-signal control alone is different.
Example: the selected route asks the model to prepare for an exit while you stay alert and ready to steer.
Adds controls for colors, icons, layouts, or extra driving information on the screen.
Some drivers want a clean stock-like display; others want more status and customization.
Example: hide visual clutter or show extra lead-car, lane, and pedal information.
Adds controls for screen recordings, trip totals, or reviewing saved driving information.
Review a past drive or saved screen capture; available history and storage depend on the project and service.
Example: save the driving screen during a trip or review recent distance totals while parked.
Reduces selected routine sounds. Which warnings remain audible depends on the fork and its settings.
Useful for reducing repeated chimes; check the exact alert policy before choosing a setting.
Example: quiet engagement chimes while retaining the warning sounds specified by that implementation.
Adds controls for saving settings, restoring them, or recovering the software after a problem.
A backup can save setup time; restoration may require the original device, keys, or compatible software version.
Example: restore your preferred settings after reinstalling a fork.
Adds a project-provided way to manage eligible settings, backups, or device information from another screen.
It can be easier than changing many options directly on the comma device.
Example: review or restore eligible settings from a phone while the car is parked.
Changes the volume of selected alert types separately. Available alerts and minimum levels differ by fork.
You may want quieter engagement chimes without using the same volume for every alert.
Example: adjust an engagement chime separately from a warning volume.
Switch manually between standard speed control and Experimental or end-to-end planning. Exact modes and car requirements depend on the fork and version.
Manual selection is different from automatically switching modes as conditions change.
Example: select a driving mode yourself instead of enabling an automatic mode-switching rule.
Provides controls for downloading updates or selecting a software branch. Branch availability and maturity differ by project.
You can see which update path you are choosing before changing the installed software.
Example: check for an update while parked and review the selected branch before installing it.
Changes the sound pack or engagement chimes where the fork and vehicle support it.
Choosing a sound is different from changing its volume or suppressing an alert.
Example: choose another engagement sound pack; some vehicle-specific settings require a restart.
Captures images after the parked device detects sustained motion. It needs power, working sensors and cameras, and the feature enabled.
You can review a detected bump or movement through the project’s event interface.
Example: sustained movement of the parked device triggers images that you later review in Galaxy.
Pairs a compatible accessory and maps supported buttons to software actions. Branch and device requirements apply.
An accessory can provide controls when the car’s own buttons are limited.
Example: pair a controller while parked and assign a supported button to a favorite action.
Choose how much the set speed changes with a short or long press of the cruise buttons. Availability depends on the car and speed-control setup.
Use smaller adjustments or reach a different set speed with fewer button presses.
Example: set a short press to change speed by one unit and a long press by five.
Applies configured changes to following distance, acceleration or curve speed using weather information. Requires a supported setup and weather data.
Keep separate preferences for rain, snow or poor visibility; this does not establish that conditions are safe to drive in.
Example: add a following-distance offset when the weather service reports rain.
Assign supported steering-wheel buttons to actions such as changing a driving mode or pausing an assistance function. Available actions depend on the car and control setup.
Put frequently used controls on a supported steering-wheel button.
Example: assign a long press of the distance button to change a driving mode.
Adds an optional reminder when a lead car moves away or the model predicts traffic can move. Available alerts differ by fork.
A reminder can help you notice movement while stopped; check the road and signals yourself before moving.
Example: a chime sounds when the stopped car ahead moves away.
Comparison refreshed Sep 5, 2026. Source dates and branch scope vary.
FrogPilot
StarPilot