spec(M1): System Presence — what Robin watches and how it surfaces alerts #5

New issue

Open

opened 2026-05-19 07:46:44 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-05-19 07:46:44 -07:00

Owner

What M1 built

Robin watches your system in the background and surfaces alerts when it recognises a known migration pain point.

What it watches

journald: systemd journal via journalctl -f -o json — catches application crashes, service failures, driver errors
kmsg / dmesg: kernel ring buffer — catches driver load failures, USB/hardware errors, out-of-memory events
inotify app logs: watches ~/.local/share/xorg/ and ~/.xsession-errors for Xorg/Wayland session errors

How alerts surface

Tray icon badge lights up (always)
Desktop toast notification (configurable: badge-only or off)
Events drain into the chat panel when you open it

Pattern files (starter set)

macos-to-arch.toml — AUR build failures, pacman lock file errors, missing .dmg-style installer confusion, Cmd-key muscle memory hints.

windows-to-debian.toml — apt lock errors, Flatpak vs apt confusion, NTFS write permission issues, snap disabled on Mint.

Configuration

~/.config/robin/config.toml:

Notification level: badge_and_toast (default) | badge_only | off
Quiet mode: suppresses toasts during focus periods

Questions for Xander

Are the CachyOS patterns catching real errors you see day-to-day, or are they missing common ones?
What would be the top 3 friction points Robin should recognise that are not in the starter set yet?
Does the tray badge + chat panel drain feel like the right UX, or would you want alerts more or less prominent?

Implementation: PR #2

## What M1 built Robin watches your system in the background and surfaces alerts when it recognises a known migration pain point. ### What it watches - **journald**: systemd journal via `journalctl -f -o json` — catches application crashes, service failures, driver errors - **kmsg / dmesg**: kernel ring buffer — catches driver load failures, USB/hardware errors, out-of-memory events - **inotify app logs**: watches `~/.local/share/xorg/` and `~/.xsession-errors` for Xorg/Wayland session errors ### How alerts surface 1. Tray icon badge lights up (always) 2. Desktop toast notification (configurable: badge-only or off) 3. Events drain into the chat panel when you open it ### Pattern files (starter set) `macos-to-arch.toml` — AUR build failures, pacman lock file errors, missing `.dmg`-style installer confusion, Cmd-key muscle memory hints. `windows-to-debian.toml` — apt lock errors, Flatpak vs apt confusion, NTFS write permission issues, snap disabled on Mint. ### Configuration `~/.config/robin/config.toml`: - Notification level: `badge_and_toast` (default) | `badge_only` | `off` - Quiet mode: suppresses toasts during focus periods ## Questions for Xander - Are the CachyOS patterns catching real errors you see day-to-day, or are they missing common ones? - What would be the top 3 friction points Robin should recognise that are not in the starter set yet? - Does the tray badge + chat panel drain feel like the right UX, or would you want alerts more or less prominent? **Implementation:** PR #2

pyr0ball added this to the M1: System Presence milestone 2026-05-19 07:46:44 -07:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/robin#5

No description provided.