// AI diagnostics for embedded Linux

AI connected.
Nothing installed.

It reads your logs, network, and services over SSH — then tells you what broken and why.

Why is the mosquitto service so slow?

› Worked for 18s

mosquitto's publish latency is high because the device is I/O-bound, not CPU-bound.

Root cause

journald is writing 2.3 GB of debug logs to /var/log on the same eMMC partition as the broker's store. The partition is at 96%, and iowait is sitting at 41% — every message blocks on a slow flush.

Evidence

  • df -h → /var at 96%
  • iostat → mmcblk0 await 380 ms, %util 99
  • mosquitto.service restart-looping on flush timeouts

Suggestions

  1. 1. Reclaim the 2.3 GB now$ sudo journalctl --rotate && sudo journalctl --vacuum-size=100M
  2. 2. Keep journald capped going forward$ echo 'SystemMaxUse=100M' | sudo tee -a /etc/systemd/journald.conf

// loop1 suggests — it never makes changes to your device

// One copy/paste

What it takes to get started.

Paste it on your device terminal — a short-lived agent connects in seconds.

curl -s https://loop1.dev/c/<token> | sh

See it run

A two-day chase, in a few minutes.

Watch the agent diagnose a real device.

loop1.dev — demo session

// Under the hood

Bring AI to your device, safely.

loop1 runs over standard SSH.

  • Zero install — No new binary, package, or persistence file will be installed.
  • Single-use key — The copy/paste command gives the device one-time connectivity to loop1.

// loop1 is designed to keep everything exactly the same before & after the session.

// Closed beta program

Wheel has started, hop in!

Engineers at Octa Lanes have been using loop1 over the past few months.

We're now ready to expand closed beta access — to help us shape loop1 into the best experience.

We're offering a free credit grant. Up to $100 in AI usage credit per account each month.

// Get $100 credit

Join the closed beta.

We'll get back to you within 48 hours — every request reaches a person.