Trojan Horse: AI agents that call mechanics for you, and how Kane CLI caught our bug

The problem Your car breaks down at night. You search for mobile mechanics and call them one by one: who’s open, who’s close, who won’t overcharge? That’s exactly when time matters most.

What we built Trojan Horse (“Engine cooked? Help booked.”) is a multi-agent app we built in one day at Kane CLI Hack Day SF:

The stack: a React dashboard, a Node orchestrator with SQLite, separate discovery and voice services, and shared zod contracts.

Why we didn’t trust our own AI A voice agent can easily invent a price, say “booked” when it isn’t, or dispatch twice. So we tested Trojan Horse with Kane CLI against our own plain-English requirements:

What Kane caught We added one rule: if a mechanic doesn’t say whether they’re free, show “Unknown”. Kane designed a test, and it failed. The mechanic said “I’m not sure anyone is free right now”, and our app showed “Available now: No”. Our shared contract stored availability as true or false, so both the simulated and the live voice path turned “unsure” into “unavailable”. A real driver would have been misled. We made the field nullable and fixed the UI, and the same test passed. Both evidence packs are in the repo.

Code: https://github.com/RamyaRamachandran-driod/emergency-caller