Live link view
Network, access point (BSSID), channel, band, width and PHY mode, with live charts of RSSI, SNR, Tx rate and probe latency, and a roam ticker. An on-demand scan shows whether a stronger access point for the same network was in range.
MacDiag
Coming soon
MacDiag watches a Mac's Wi-Fi link, connection checks and system logs, and when something goes wrong it saves an evidence bundle — the minutes before, during and after — that you can line up with your access point and RADIUS logs.
…:3a:10 → …:7c:42The problem
Wi-Fi complaints reach IT after the problem has passed, with no timestamp and no detail. Your wireless controller shows the access point's side. The client's side — what signal the Mac had, which access point it was on, whether the gateway or DNS stopped answering — is usually missing. MacDiag fills that gap.
What it does
Everything lands on one timeline with UTC timestamps, so it lines up with your access point, controller and RADIUS records.
Network, access point (BSSID), channel, band, width and PHY mode, with live charts of RSSI, SNR, Tx rate and probe latency, and a roam ticker. An on-demand scan shows whether a stronger access point for the same network was in range.
Continuous checks against the default gateway, DNS resolvers and internal and external targets you choose — packet loss, latency, jitter and DNS resolution time — so “connected but nothing works” shows up as data.
Sensor samples and Wi-Fi system log lines are kept in a rolling buffer. When something happens, the minutes before it are already recorded — you don't have to be watching.
Built-in rules for disconnects, authentication failures, roam storms, weak signal and “associated but no traffic”. Any metric, event or log pattern can trigger a marker, a bundle or a debug-logging session, with cooldowns and disk quotas.
Press ⌃⌥⌘M anywhere to type a note — “Zoom froze in room 204” — and it's stamped onto the same timeline as the machine data. Notes can also be added after the fact.
One folder with a manifest, the timeline window, Wi-Fi snapshots and scan results, a system log extract, and network state: interfaces, routes, DNS, DHCP lease and probe results. Capture by hand, or let a rule do it.
Evidence bundles
A capture covers the last five minutes and keeps recording for two more, then writes everything to a single folder. The manifest records exactly what was collected and why, so a bundle can go to a vendor or into a ticket as-is.
Bundles are kept for 14 days by default under a size quota, oldest first out. Both are adjustable.
bundle-20261114T160211Z-host/
manifest.json trigger, rule, OS, hardware
timeline.jsonl samples, events, comments
wifi/ link snapshots, scan results
logs/ unified log extract
net/ ifconfig, routes, DNS, DHCP,
ARP/NDP, probe results
pcap/ only if capture is enabled
Controls
One click each, all logged. Controls that change a setting remember the previous value and offer a revert; some revert automatically on quit or after a timer.
Root-only work runs in a small helper. It never takes a shell string: each request maps to one fixed, allow-listed command with checked arguments, and it verifies the app's code signature on every connection.
Viewing and adding comments need nothing. Controls that change system state, packet capture and sysdiagnose ask for an administrator. You can tighten or loosen each tier per device group with a configuration profile.
Every privileged action goes into an audit log — who, when, what and the result. A menu bar indicator shows whenever a capture or debug session is running.
Deployment
Made for schools and organizations that manage their Macs centrally on enterprise Wi-Fi.
.pkg installs the app and its helper — upload it to Mosyle, Jamf Pro or another MDM.Privacy
Roadmap
MacDiag is built as a host for diagnostic modules. Wi-Fi is the first; these are planned, not yet available.
MacDiag is in development. Email us and we'll let you know when it launches, along with pricing.
App Store apps are sandboxed, which blocks the privileged helper, system log streaming and the network commands MacDiag relies on. It's distributed directly as a Developer ID–signed, Apple-notarized package instead.
It's built for Apple silicon Macs on macOS 15 Sequoia or later.
macOS hides the Wi-Fi network name and access point (SSID and BSSID) from apps without Location permission, and an MDM can't grant it ahead of time. MacDiag explains this on first run. If a user declines, everything except the network name and access point still works.
No. MacDiag observes, records and offers controls; a person decides what to change. Every change is logged and can be reverted.
A menu bar indicator shows whenever a capture or debug session is active, and each bundle's manifest lists what was collected. Whether users can stop the helper is up to your MDM configuration.
Launch news and pricing only. Interested in piloting it on your network? Say so in the email.
Get notified