I built probeTool because I wanted something I could actually run locally against my own projects without sending code to some third-party service.
You install it as a single Go binary, via a curl install script, or manual download, point it at a directory, and it runs a full or quick scan using an AI agent backed by Claude (or any OpenRouter-compatible model you configure). Results get stored in a local SQLite database and rendered in an embedded Next.js dashboard that opens on localhost.
There's also a system tray mode that keeps it running in the background, polls for updates every few hours, and gives you a menu bar shortcut to open the dashboard.
The whole thing ships as a proper versioned release with GitHub Actions CI, auto-update support, and a Homebrew tap — so it behaves like a real distributed tool rather than just a script.
Current implementation drawbacks and hurdles
NextJS is really not the right tool for this. I picked it for this project simply because I wanted a framework I know like the back of my hand. I've never shipped bundled code like this, which meant I never thought about how I would embed NextJS into the Go bundle. I didn't know I would need to bundle node, and how big my bundle would need to be let alone how difficult it would be to even do that. Needless to say, I'm switching to Svelte or HTMX.
It needs to be easier to customise what "full" or "quick" scan is and I need to make the scans more deterministic.