WikiBeta

1Image: /api/wiki/asset/frogpilot/assets/toggle_icons/icon_discord.png
2Contributors:

FrogPilot is built and maintained by a community of contributors, testers, and everyday drivers. Whether you need help troubleshooting a problem, want to report a bug, submit a custom theme, or contribute code, there's a channel designed for you. Several in-app settings connect your device directly to these community channels, and this guide walks you through every one of them.

Before You Start

You don't need any accounts to use FrogPilot, but having a Discord account and/or a GitHub account unlocks the full community experience.

A Discord account lets you chat with other users, get real-time help, and ensures the development team can follow up when you submit a bug report from your device. A GitHub account lets you file detailed bug reports, request features, and contribute code.

You don't need to configure any of the settings described in this guide for FrogPilot to work normally. All of the community-related parameters are optional, and your device will drive just fine without them.

1. Join the Discord Server

The FrogPilot Discord server is the main hub for real-time support, feature discussions, and community interaction.

How to join:

1. Visit discord.gg/FrogPilot.
2. Create a Discord account if you don't have one.
3. Read the server rules and introduce yourself.

What you'll find there:

The Discord server typically includes channels for general discussion, support requests, bug reports, theme sharing, development updates, and announcements.

💡 Tip: If you're new to FrogPilot, start in the support or general channels. Experienced users and contributors are often happy to help with setup questions, car compatibility, and tuning advice.

2. Set Your Discord Username on the Device

Your device can send bug reports directly to the FrogPilot development team through Discord. Setting your Discord username lets them follow up with you if they need more information.

Where to set it:

1. On your device, go to FrogPilot → System Settings → Utilities.
2. Tap Report a Bug or an Issue.
3. When prompted, enter your Discord username. The device saves it for future reports.

You can also enter your username during the bug report flow itself. Once set, it's stored on the device and pre-filled the next time you submit a report.

Property	Value
Parameter	Discord Username
Default	(empty)
Tuning Level	Minimal
Purpose	Associates your device's bug reports and theme submissions with your Discord identity

Leaving this blank is perfectly fine for everyday use. The device doesn't require it for any driving functionality. It's only used when you actively submit a bug report or a theme through The Pond.

3. Submit a Bug Report (In-App)

The fastest way to report a problem is directly from your device. FrogPilot sends your report to the development team's Discord channel automatically.

Step by step:

1. Make sure your device is connected to the internet (Wi-Fi or cellular).
2. Go to FrogPilot → System Settings → Utilities.
3. Tap Report a Bug or an Issue.
4. Choose the issue that best describes what you're experiencing from the list. Options include things like "Steering feels twitchy or unnatural", "The car doesn't follow curves well", "openpilot disengages when I don't expect it", and more.
5. For some issues (like "Something else"), you'll be asked to type a short description of what's happening (up to 300 characters).
6. Enter your Discord username when prompted. If you've entered it before, it's pre-filled.
7. Tap Send Report. You'll see a confirmation that the report was sent.

What gets included in the report automatically:

• Your selected issue description
• Your Discord username
• The error log from your device (if one exists from a recent crash)
• Your current toggle/settings configuration

The development team receives this as a formatted message in their Discord channel, along with your settings file as an attachment. This gives them everything they need to start investigating.

⚠️ Warning: The in-app report button is only available on official FrogPilot builds. If you're running a custom fork or a modified build, the button won't appear. In that case, use the manual GitHub issue process described below.

4. File a Bug Report on GitHub (Manual)

For complex issues that need detailed reproduction steps, screenshots, or logs, filing a GitHub issue is the better choice.

Step by step:

1. Go to github.com/FrogAi/FrogPilot/issues.
2. Click New Issue.
3. Write a clear, descriptive title (e.g., "Car brakes too hard when approaching stopped traffic on 2024 Toyota RAV4").
4. In the description, include:

• Branch name: Which FrogPilot branch you're running (e.g., FrogPilot, FrogPilot-Staging, FrogPilot-Testing)
• Car make, model, and year: e.g., "2023 Hyundai Ioniq 5"
• Dongle ID: Your device's identifier (see section 6 below for how to find it)
• What happened: Describe the unexpected behavior clearly
• Steps to reproduce: What were you doing when the issue occurred? Can you make it happen again?
• What you expected: What should have happened instead?
• Whether it's reproducible: Does it happen every time, or only occasionally?

5. Submit the issue.

When to use GitHub instead of the in-app report:

• The issue is complex and needs a back-and-forth discussion with code references
• You have screenshots, video clips, or log files to attach
• You want to track the issue's progress publicly
• The in-app report button isn't available on your build

5. Browse and Contribute on GitHub

FrogPilot's development happens across two main GitHub repositories.

The main repository: FrogAi/FrogPilot

This is where all of FrogPilot's source code lives. You can:

• Browse open issues to see known bugs and their status
• Read pull requests to see what features are in development
• Fork the repo and submit your own pull requests if you want to contribute code
• Check the README for installation instructions and supported vehicles

The resources repository: FrogAi/FrogPilot-Resources

This companion repository stores all the downloadable assets your device fetches automatically:

• Driving models: The AI models that handle steering and speed decisions (stored on the Models branch, with compiled tinygrad models in a compiled subdirectory)
• Map daemon: The mapping service binary used for offline map features. The primary download comes from a separate community repository (pfeiferj/openpilot-mapd), with the resources repository's Mapd branch on GitLab serving as a fallback source
• Themes: Color schemes, icon packs, sound packs, turn signal animations, and distance icons (stored on the Themes, Distance-Icons, and Steering-Wheels branches)
• Tinygrad runtime: The machine learning framework used to run newer driving models (stored on the Tinygrad branch)
• Version metadata: Model and map daemon version information (stored on the Versions branch)

When you download a new driving model or theme from FrogPilot's settings, your device fetches it from this resources repository (with GitLab as a fallback if GitHub is unavailable). You don't need to visit this repository directly; it's all handled automatically through the in-app download screens.

A separate submissions repository (FrogAi/FrogPilot-Resources-Submissions on GitLab) receives theme submissions from users through The Pond, FrogPilot's built-in theme creation and browsing tool. This is distinct from the main resources repository used for downloads.

6. Find Your Dongle ID

Your dongle ID is a unique identifier for your device. Support staff and developers often ask for it when helping you diagnose issues, because it lets them look up your device's stats and drive history.

FrogPilot actually uses two different dongle IDs:

comma Dongle ID: This is the standard device identifier assigned by comma.ai's servers. You can find it in the main openpilot settings under the Device section, where it's displayed as "Dongle ID". This is the one most people refer to when they say "dongle ID".

FrogPilot Dongle ID: This is a separate, randomly generated 16-character identifier that FrogPilot creates automatically the first time your device boots. It's used internally for anonymous usage statistics and model scoring. You don't need to configure it, and it isn't displayed anywhere in the standard UI. If you need to access it, you can find it stored as the FrogPilotDongleId parameter through SSH.

There's also a Konik Dongle ID that's created if you use the alternative Konik cloud server instead of comma connect. It's generated automatically when Konik mode is enabled and you don't need to interact with it directly.

💡 Tip: When someone in the Discord asks for your "dongle ID", they usually mean the comma Dongle ID shown in your device's settings. Include it in bug reports so the team can look up your device's drive logs.

7. Set Up SSH Access (Developers Only)

SSH gives you remote command-line access to your device over your network. This is useful for developers and advanced users who want to inspect logs, modify files, or debug issues directly.

⚠️ Warning: Regular users don't need SSH access. Only set this up if you're comfortable with a command-line terminal and understand the security implications. Never enter a GitHub username other than your own. A comma employee will never ask you to add their GitHub username.

Step by step:

1. Make sure you have a GitHub account with at least one SSH public key added to it (under GitHub → Settings → SSH and GPG keys).
2. On your device, open the main openpilot Settings (not FrogPilot settings) and navigate to the Device section.
3. Find the SSH Keys option and tap ADD.
4. Enter your GitHub username. The device fetches your public SSH keys from GitHub automatically.
5. If your username has keys on GitHub, they'll be loaded onto the device. If not, you'll see an error.
6. Once keys are loaded, you can SSH into your device using its IP address on your local network.

Setting	Default	Tuning Level	Purpose
Discord Username	(empty)	Minimal	Associates device reports with your Discord handle
FrogPilot Dongle ID	(auto-generated)	Minimal	Device identifier used in community reporting and stats
GitHub SSH Keys	(empty)	Minimal	Public SSH key(s) for remote device access
GitHub Username	(empty)	Minimal	GitHub identity for SSH key deployment
SSH Enabled	Off	Minimal	Enables the SSH daemon on the device

8. Submit a Custom Theme

FrogPilot includes a built-in tool called The Pond where you can create and submit custom themes (color schemes, icons, sounds, steering wheel images, and distance icons) directly from your device. When you submit a theme, it's sent to the FrogPilot-Resources-Submissions repository on GitLab (separate from the main resources repository used for downloads) and a notification is posted to the development team's Discord channel.

Your Discord username is included with theme submissions so the team can credit you and follow up if needed. This is another reason to set your Discord username in the device settings.

Recommended Setups

Different users need different levels of community engagement. Here's what to set up based on your role.

User Type	Discord	GitHub Account	SSH Access	Discord Username on Device
Active community member	Join and participate	Helpful for tracking issues	Not needed	Yes, set it
Developer/contributor	Join for coordination	Required	Yes, set up SSH keys	Yes, set it
Everyday driver	Join for help and updates	Optional	Not needed	Optional, but helpful if you plan to report bugs
Theme creator	Join to share your work	Optional	Not needed	Yes, set it so you get credit

Troubleshooting

Answers to common questions about getting help and participating in the FrogPilot community.

Q: Can I request support for a car that isn't currently supported?

A: Vehicle support depends on openpilot's underlying compatibility, which requires reverse-engineering the car's communication network. You can check comma.ai's supported vehicle list and openpilot's community resources for ongoing porting efforts. If your car is supported by openpilot but has issues specific to FrogPilot, that's a great candidate for a bug report. If your car isn't supported by openpilot at all, that's outside FrogPilot's scope, as it requires work at the openpilot level.

Q: Do I need a GitHub account to get support?

A: No. Most users get help through the FrogPilot Discord server, which doesn't require a GitHub account. A GitHub account is only needed if you want to file formal bug reports, track issues, or contribute code.

Q: I enabled SSH but can't connect to my device. What are common causes?

A: First, make sure the SSH Enabled toggle is turned on in the device settings. Verify that your GitHub account actually has SSH public keys uploaded (check GitHub → Settings → SSH and GPG keys). Your device and computer must be on the same network. Try pinging your device's IP address first. If you recently added keys, you may need to reboot the device. Also confirm you're using the correct SSH command (typically ssh comma@<device-ip>).

Q: I set my Discord username on the device, but nobody has responded to my bug report. What should I check?

A: The in-app report is a one-way message to the development team. They receive it, but there isn't a built-in reply mechanism on the device. Check the FrogPilot Discord server directly for any follow-up questions from the team. Make sure your Discord username is spelled correctly (including any special characters) so they can find you on the server. Also keep in mind that support is provided by volunteers, and response times vary.

Q: The in-app "Report a Bug or an Issue" button isn't showing up. What's wrong?

A: The report button only appears on official FrogPilot builds. If your device is running a different fork or a custom build, the button is hidden. You can still report bugs by filing a GitHub issue at github.com/FrogAi/FrogPilot/issues or by posting in the FrogPilot Discord support channels.

Q: The in-app bug report says I need to connect to the internet. I thought I was connected.

A: The device checks for an active internet connection before allowing you to send a report. Make sure your device is connected to Wi-Fi or has a working cellular connection (through comma prime or a hotspot). If you just connected, give it a moment and try again.

Q: Where do I find my dongle ID?

A: Open the main openpilot Settings (not FrogPilot settings) and look in the Device section. Your comma Dongle ID is displayed there. This is the identifier you should include in bug reports and support requests.

Q: Where do I submit a custom theme?

A: Use The Pond, FrogPilot's built-in theme tool. You can access it directly on your device. When you submit a theme, it's sent to the FrogPilot-Resources-Submissions repository on GitLab and the development team is notified through Discord. Make sure your Discord username is set on the device so you get proper credit for your creation.

Q: Where should I post feature requests?

A: The best place to suggest new features is in the FrogPilot Discord server. For well-defined, detailed proposals with technical specifics, you can also open a GitHub issue or discussion at the FrogPilot repository.

Q: Who maintains the FrogPilot-Resources repository?

A: The FrogPilot development team maintains the resources repository. It hosts all downloadable driving models, themes, and other assets that your device fetches automatically. Community members can contribute themes through The Pond's submission process (which sends them to a separate submissions repository for review), but driving models and core assets are managed by the development team.

Q: I'm using FrogPilot-Staging or FrogPilot-Testing. Should I report bugs differently?

A: Include your branch name in every bug report. Staging and Testing branches contain features that are still being developed, so some issues may already be known. Check the Discord announcements channel for known issues on your branch before reporting. The in-app report tool automatically includes your toggle settings, which helps the team identify branch-specific problems.

Limitations

The FrogPilot community is helpful, but there are boundaries to what volunteer-driven support can address.

• Cellular/carrier issues are outside scope. If your device's SIM card or data plan isn't working, that's a carrier or comma prime issue, not something the FrogPilot community can troubleshoot.
• Hardware failures go to comma.ai. If your comma 3X, comma four, or other comma device has a physical defect (broken screen, overheating, camera failure), contact comma.ai's support directly. The FrogPilot community can't repair hardware.
• Non-FrogPilot forks are out of scope. If you're running SunnyPilot, DragonPilot, or another openpilot fork, the FrogPilot community can't help with fork-specific issues. Each fork has its own community channels.
• Professional vehicle service can't be replaced. If your car has a mechanical problem, warning light, or safety recall, take it to a qualified mechanic or dealer. FrogPilot is a driver assistance system, not a replacement for vehicle maintenance.
• Support is best-effort from volunteers. Response times vary. The development team and community members help when they can, but there are no guaranteed response times or service-level agreements.

Related Features

These FrogPilot features connect to the community channels described in this guide.

Feature	Relationship	How it interacts
Driving Model Selection	Works alongside	Driving models are downloaded from the FrogPilot-Resources repository. Model scoring data tied to your FrogPilot Dongle ID is uploaded to help the community evaluate model quality.
The Pond	Works alongside	The Pond is FrogPilot's built-in theme creation and browsing tool. Theme submissions from The Pond are sent to the submissions repository (FrogAi/FrogPilot-Resources-Submissions on GitLab) and notified through Discord using the same webhook system described in this guide. Your Discord username is included with submissions.