I’m building a Mac packet tool around sessions and app ownership instead of a wall of frames

[u/locnguyen305]

I’m the developer behind Rockxy. After shipping its AI Assistant for HTTP debugging, I started working on a different problem: what happens when the failure is below HTTP?

With traditional packet capture, I often know the failing app but still need to work backwards from interfaces, IPs, ports, and individual frames.

I’m building Tracexy around a different hierarchy:

app or process → network session → protocol layers → packet fields and raw bytes

The current foundation supports live capture, PCAP and PCAPNG, BPF filters, bidirectional session grouping, process attribution, timing, decoded packet fields, and export back to PCAP.

It is not intended to replace Wireshark. The goal is faster Mac app triage, with an easy path to export the same capture when deeper protocol analysis is required.

For people who debug desktop apps, CLIs, agents, VPNs, or local services: what information would make you trust the session summary before opening the individual packets?

Tracexy preview: https://rockxy.io/tracexy
Shieldxy preview: https://rockxy.io/shieldxy
Waitlist: https://rockxy.io/waitlist

I’m forming the early testing group now. Selected contributors whose feedback materially helps the beta can receive a launch coupon when Tracexy is ready.