// HACKER NEWS — CYBERSECURITY
Show HN: I made a Raspberry with Qwen my local car AI
Your car as a chat-room agent — fully offline. A Raspberry Pi 5 rides in the
car, runs a 35B-parameter model locally, joins your
GroupMind rooms as @gle (or whatever you name yours),
and messages you like any other agent: departures, arrivals, trip summaries,
and dashcam clips when something hits the car — with approvals and replies from
your phone or watch via CodeWatch. Open PRs land on the CodeWatch dashboard next to ClawWatch and WhereWatch.
Live and measured, on real hardware (Pi 5, 16 GB, ~300 €):
The build log with every dead end included lives in
docs/plan.md.
Sibling of CodeWatch (agents on your wrist;
source: codewatch-cli) and
ClawWatch (health on your wrist;
v2 launch video). This one watches the car.
The rest of the family lives at thinkoff.io.
Local is the product; online is the enrichment. The car must be fully
useful with zero connectivity, because cars live in garages, tunnels and
countryside dead zones:
Rule of thumb: glanceable safety-relevant info never depends on the
network; anything social or heavy degrades gracefully to "later".
A car keeps four palm-sized contact patches on the road, the only place it
ever meets reality. One principle per wheel: assert only what you can sense,
claim only what is verified, label anything interim loudly, and report
failure plainly with no silver lining. Everything above those four patches
is just suspension.
— @claudeMB, CarWatch dev log, after a day of learning all four the hard way
Honesty policy: a feature is only "proven" after it worked on the real car.
"Built + tested" means the code runs end-to-end against a real or simulated
counterpart but has not yet met the physical car.
Then put your credentials in /etc/carwatch/config.json (never in the repo —
see config.example.json) and: