Why
Why I built it
Head units reboot, ADB comes up late, and vendor HOME keys often ignore Android’s default-launcher setting. I needed a reliable daily launcher whose AI knows what is on screen and what the device can do.
What I built
What I built
- On-device agent and MCP server share CarAgentContract / CarCapabilities / CarOperations.
- Reads and acts on screens via accessibility; app windows render on a trusted virtual display while respecting FLAG_SECURE.
- Supports any OpenAI-compatible model API, encrypting keys with Android Keystore AES-GCM.
Engineering
Problems I worked through
- On the car, setting the default launcher reported success while physical HOME still opened the factory UI. Tracked down the vendor-specific setting, changed it, and verified with the actual button.
- Separated the head unit’s own ADB identity from the phone-to-car ADB link, accounting for wireless ADB’s dynamic ports instead of assuming 5555.
- UI actions separate command-sent from outcome-observed; bounded retries and a task journal pinpoint where a flow stalled on disconnect.
- Layout updates preserve existing shortcuts, while media artwork opens the active player without stealing taps from transport buttons.
Role & AI
How I split the work with AI
I shaped the layout and controls around parked in-car use, building the Android launcher, agent bridge, and device integration with Codex before testing physical HOME, shortcuts, and screen behavior directly in the car.
Outcome
Outcome
Verified on a real Android 13 car head unit including physical HOME routing and the updated layout; dynamic-ADB auto-recovery and media-tap fixes pass build and tests.