QVAC

Automotive

OBDient

An offline automotive co-pilot that reads live OBD-II sensors and diagnoses issues in plain language

ragmulti-agentp2p-mesh
OBDient

Most car-diagnostic apps are a cloud LLM behind a chat box. OBDient plugs into any ELM327 OBD-II adapter, reads a car's engine live, and diagnoses faults in plain language through a compact model - CARpsy - that runs entirely on the phone via the QVAC SDK.

A knowledge graph, not a flat index

Instead of a flat vector lookup, OBDient's retrieval layer - SHIMI - is a confidence-weighted knowledge graph built on a SKOS ontology, so a question about one fault code automatically pulls in the ignition and fuel-system knowledge a real mechanic would also reach for. A node's confidence only rises once a repair's outcome is independently verified against the car's own data, never a same-session thumbs-up, which is how the system keeps validated knowledge separate from unverified guesses.

SHIMI hierarchy (README.md)
P0301 (cylinder-1 misfire)
   └─ misfire_random        ← the canonical concept
        ├─ ignition         ← ancestor knowledge
        ├─ fuel_system      ← related branch
        └─ powertrain       ← parent domain

Multi-agent by design

A deterministic state machine - not a learned router - splits the job across roles: a template interviewer collects the case for free, CARpsy diagnoses from it offline, and a cloud senior advisor is reached only if the owner explicitly opts in, and never receives the VIN, plate, or raw sensor readings.

Demo video

Why the graph gets smarter, not just bigger

  • SHIMI retrieves related meaning through a knowledge-graph hierarchy, not just similar words

  • A repair only strengthens the graph once the car's own outcome confirms it worked

  • The private on-device path is the default; a cloud advisor is a single opt-in escalation

Build this

Ship your own local AI

One install in JavaScript or Python. 10+ AI tasks. Private, offline and free - on the hardware you already own.