What are your AI tools really doing on your machine?
Free, open-source dashboard that shows which AI tools run on your computer, what they connect to, what they can access and how many tokens they use. Local and read-only: no cloud, no account. macOS, Linux, Windows (beta).
Hi Product Hunt 👋 I'm Safa, the maker of SecAIQ Watch.
AI assistants now read our project files, run commands and connect to MCP servers, yet most of us can't say what they are connected to or allowed to touch. I built SecAIQ Watch to make that visible on my own machine.
What it does: • Detects ~37 AI tools and ~33 providers (coding agents, chat apps, AI editors, local models, MCP servers) • Shows live connections and bytes sent/received per tool • Maps each tool to sensitive areas: SSH keys, .env files, cloud credentials, browser data, keychain • Flags risky settings and gives a posture grade from A to F • Tracks token usage for Claude Code and Codex • Exports reports and an AI-BOM (CycloneDX 1.5)
How it stays safe: it is local and read-only, it never sees prompts or file contents, the panel only answers on 127.0.0.1, and it loads no third-party code.
It's a beta and I want to be upfront about that. It works well on macOS. Linux and Windows have only been tested against sample command output so far, and Windows can't report per-connection byte counts at all. That is exactly where your feedback helps most: run `php bin/diagnostics.php` and open a GitHub issue if something looks off.
It is MIT-licensed and needs only PHP 8.1+ with SQLite (no Composer, no database server, no account). There is a built-in demo mode with synthetic data if you'd rather explore before pointing it at your own machine.
What would you want it to show that it doesn't yet?
About SecAIQ Watch on Product Hunt
“What are your AI tools really doing on your machine?”
SecAIQ Watch launched on Product Hunt on September 21st, 2026 and earned 70 upvotes and 6 comments, placing #25 on the daily leaderboard. Free, open-source dashboard that shows which AI tools run on your computer, what they connect to, what they can access and how many tokens they use. Local and read-only: no cloud, no account. macOS, Linux, Windows (beta).
On the analytics side, SecAIQ Watch competes within Open Source, Privacy, Artificial Intelligence and GitHub — topics that collectively have 600.7k followers on Product Hunt. The dashboard above tracks how SecAIQ Watch performed against the three products that launched closest to it on the same day.
Who hunted SecAIQ Watch?
SecAIQ Watch was hunted by Safa Paksu. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of SecAIQ Watch including community comment highlights and product details, visit the product overview.
Safa Paksu
Hi Product Hunt 👋 I'm Safa, the maker of SecAIQ Watch.
AI assistants now read our project files, run commands and connect to MCP servers, yet most of us can't say what they are connected to or allowed to touch. I built SecAIQ Watch to make that visible on my own machine.
What it does:
• Detects ~37 AI tools and ~33 providers (coding agents, chat apps, AI editors, local models, MCP servers)
• Shows live connections and bytes sent/received per tool
• Maps each tool to sensitive areas: SSH keys, .env files, cloud credentials, browser data, keychain
• Flags risky settings and gives a posture grade from A to F
• Tracks token usage for Claude Code and Codex
• Exports reports and an AI-BOM (CycloneDX 1.5)
How it stays safe: it is local and read-only, it never sees prompts or file contents, the panel only answers on 127.0.0.1, and it loads no third-party code.
It's a beta and I want to be upfront about that. It works well on macOS. Linux and Windows have only been tested against sample command output so far, and Windows can't report per-connection byte counts at all. That is exactly where your feedback helps most: run `php bin/diagnostics.php` and open a GitHub issue if something looks off.
It is MIT-licensed and needs only PHP 8.1+ with SQLite (no Composer, no database server, no account). There is a built-in demo mode with synthetic data if you'd rather explore before pointing it at your own machine.
What would you want it to show that it doesn't yet?