MacDiag Coming soon

See what the Mac saw when the Wi-Fi dropped.

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.

  • ✓ macOS 15 Sequoia or later
  • ✓ Apple silicon
  • ✓ Signed .pkg for your MDM
Timeline
  1. sampleRSSI −64 dBm · SNR 31 dB · ch 37 (6 GHz)
  2. eventRoam …:3a:10 → …:7c:42
  3. sampleRSSI −79 dBm · Tx rate 24 Mb/s
  4. logairportd: beacon loss
  5. probeGateway loss 100% · DNS timeout
  6. comment“Zoom froze in room 204”
  7. ruleAssociated but no traffic → bundle captured
Illustration of the kind of timeline MacDiag records.

The problem

“The Wi-Fi was bad in room 204” is hard to act on.

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

Catch intermittent problems in the act

Everything lands on one timeline with UTC timestamps, so it lines up with your access point, controller and RADIUS records.

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.

Connection checks

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.

Always-on history

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.

Rules that capture for you

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.

Comments on the timeline

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.

Evidence bundles

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

Five minutes before, two minutes after

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

The Terminal commands you'd otherwise look up

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.

Logging & capture

  • Wi-Fi debug logging
  • Raise Wi-Fi log level, auto-revert after 15 min
  • EAPOL / 802.1X verbose logging
  • Packet capture ring (headers only)
  • Wireless Diagnostics archive
  • sysdiagnose
  • networkQuality throughput test

Radio & association

  • Power-cycle Wi-Fi
  • Disassociate without forgetting the network
  • Force a rescan
  • AWDL off, to rule out AirDrop/AirPlay channel hopping
  • Private Wi-Fi address toggle

IP layer & saved state

  • Renew DHCP lease, show the lease packet
  • Flush DNS cache
  • IPv6 off / automatic
  • Temporary DNS server override
  • List and remove preferred networks
  • Show installed Wi-Fi and 802.1X profiles

A helper that can't be misused

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.

Tiered access

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.

Audited and reversible

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

Built for managed fleets

Made for schools and organizations that manage their Macs centrally on enterprise Wi-Fi.

  • One signed, notarized .pkg installs the app and its helper — upload it to Mosyle, Jamf Pro or another MDM.
  • Settings arrive by configuration profile: access tiers, default rules, probe targets, retention and disk quota.
  • Pre-approve the helper with a managed background-items profile so users can't switch it off.
  • Rules are stored as files, so the same set can be shared and pushed to every Mac.
  • One limit to know: macOS only shows a Wi-Fi network's name and access point to apps with Location permission, which each user grants once. Everything else works without it.

Privacy

Diagnostics stay on the Mac

  • No server, no account, no telemetry. Bundles are local files until someone exports them.
  • Packet capture is off by default, headers-only when on, and needs an administrator.
  • Each bundle's manifest lists exactly what was collected, for your district or company policy review.
  • This website has no analytics or tracking.

Roadmap

Wi-Fi first. More modules to follow.

MacDiag is built as a host for diagnostic modules. Wi-Fi is the first; these are planned, not yet available.

  • Hardware health Battery, SSD health and free space, thermal throttling, memory pressure and panic reports.
  • Cart Wi-Fi survey Walk a building with a cart of Macs and get findings per room.
  • Fleet coverage Opt-in background scans combined into per-access-point statistics.
  • More network modules 802.1X/RADIUS client view, wired Ethernet, DNS/DHCP and VPN.

FAQ

When is it available?

MacDiag is in development. Email us and we'll let you know when it launches, along with pricing.

Why isn't it in the Mac App Store?

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.

Does it work on Intel Macs or older macOS?

It's built for Apple silicon Macs on macOS 15 Sequoia or later.

Why does it need Location permission?

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.

Does it fix problems automatically?

No. MacDiag observes, records and offers controls; a person decides what to change. Every change is logged and can be reverted.

Can users turn it off or see what it collects?

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.

Want to know when MacDiag launches?

Launch news and pricing only. Interested in piloting it on your network? Say so in the email.

Get notified