TL;DR: I built an AI brain for all Droid Depot Droids.**
(bottom of the release notes (not the full page), in the “Assets” area)
For a while now I have been working on something that I’ve been extremely excited to share with everyone and I think it’s finally ready for final checks and I could use your help in testing.
Super Quick backstory: If you’ve bought/built a Droid at the Droid Depot, you likely loved the idea of owning your own [custom] droid and it was amazing for the time it was in Batuu when it felt alive and responsive. But once home, you realized you essentially bought a RC-car that chirps and so to the shelf or closet it went? Rarely, if ever, to be interacted with again.
What if that same behavior you experienced in Batuu could be at home? Wait, not only that – what if your droid acted like an actual DROID? So with that question in mind, I am thrilled to introduce the Kinetic Yammering and Behavioral Engine Routines project.
Or KYBER, for short.
Like the Kyber crystals that determine the color and sound of a lightsaber, KYBER alters the personality and responsiveness of a droid. And there’s zero modification to make to the droid. And it works with ALL Droid Depot droids.
ok… that was a little sales-pitch-y. Sorry.
What actually is “KYBER”?
In short: it allows you to talk with your droid and have it talk back to you (well, beep back at you). No controllers, no wake words, no command prompts.
Think of it like having a blind robo-dog.
Whether you built a custom droid or bought a prebuilt one, KYBER leans into both. You choose which model of droid you’re running, and you set its personality using 5 sliders (with 4 pre-determined character profiles included), and you have the ability to tailor its chirps and responses to how you want it to react (which you likely need to do if you have a First Order chip installed, because it likely responds way different than the default droid)
What do i need you to do?
Just…talk to your droid. Run the installer, watch your droid no longer be a dummy-bot rc-car but rather an actual character.
And then report back if you run into any issues or if you have any feedback.
Couple of important notes
- Req Specs:
- OS: A PC running Windows 10 or 11. (A Mac version is on the way, but it’ll be a little longer. I was too excited to share to wait for it.)
- Storage: At least 5GB of free hard drive space.
- Hardware: A microphone and Bluetooth 4.0 (or later) compatibility.
- Network: An active network connection for the initial setup.
- A Critical Note on Privacy:
KYBER runs a fully local language model right on your machine. Your voice and your conversations never leave your PC — nothing is sent to me, to any cloud service, or to any AI company, and nothing you say is ever saved to your disk. It’s just you and your droid. - App & Controller Compatibility:
While connected to KYBER, the droid will not be able to be used with the physical controller or the official Droid Depot app. That said, all stock droid functionality remains entirely intact. There are zero hardware or firmware changes being made to the droid. As soon as you disconnect KYBER, the physical controller and app will work perfectly again, and you can return it to its “RC-car-that-chirps” status whenever you want.
Where do I get it?
I’m hoping to eventually have it go up on the windows app store, but for now, you can find it in my fancy schmancy new GitHub
update 07/25/26 - i had to take down the build to adddress a bug. new one coming soon
Two things to expect to avoid freakouts.
- Windows may throw up a blue “Windows protected your PC” pop-up. This is not a virus warning. It shows up for basically any installer that hasn’t been “code-signed” (a certificate that costs money, which a free hobby project like this ain’t gonna have). Just click More info → Run anyway. If your antivirus throws a fit too, same story, false alarm for the same reason.
- The first launch grabs its brain. The very first time you open it, KYBER downloads its local AI (~5GB). One time only and it might take a few.
From there it walks you through connecting to the droid and giving it its persona, and then… go say hi to it.
Hit a snag? Something act weird? Droid do something unexpected (and/or hilarious)? Reply right here in the thread or use the feedback form on github. Screenshots, the exact error text, “it did this and I expected that” — all of it is helpful. That real-world feedback is exactly what I’m hoping for before this goes wider. Do keep in mind though that these droids are imprecise by default so if it overshoots or undershoots a motion, try to give it some leeway because I can only dial in their motions so much .
Thank you!!
