I built an Open-Source for tracking AI tool issues
The pain point: when Claude Code, Codex, Cursor, Antigravity or other AI tools feel broken or unusually slow, reports and signals are scattered across official status pages, Discord, Reddit and X. Official status can also lag behind what users are already experiencing.
Not Just You is meant to make those scattered signals easier to collect and check in one place.
If AI coding tool is still usable, you can check status from inside tool with the plugin or MCP. If it is down, you can still check from the CLI or the web dashboard.
Not Just You also supports optional, metadata-only local failure reporting. It can report issues automatically when enabled, without sending prompts, messages, files, diffs, commands, outputs, API keys, or account identifiers.
Repo: https://github.com/dobbylee/notjustyou
Dashboard: https://notjustyou.dev
I like that you're treating community signals as a complement to official status rather than assuming the official page is always the ground truth. When lots of users notice degraded performance before a provider updates their status page, that lag becomes a real usability problem. Bringing those signals together without collecting sensitive user data feels like the right trade-off.
Thank you for your comment
You're welcome.
One thing I'm curious about: if community signals consistently contradict the official status page, which one do you think users should ultimately trust?
That feels like a product decision as much as a technical one.
That is exactly the product decision behind Not Just You.
I don't see community signals as a replacement for official status. Official status should remain the source of truth for what the provider has acknowledged.
The core question Not Just You tries to answer is different: "Are other people seeing the same issue as me right now?"
If enough user-side signals are collected in a meaningful way, they can become a reliable early signal, sometimes faster than official status. Not because they are more authoritative, but because they reflect what users are experiencing before an incident is officially confirmed.
That's a helpful answer.
Reading it, I think there's one strategic consequence of that decision that becomes much more important as Not Just You grows, but I don't think I can explain it properly in a thread without oversimplifying it.
If you're interested, what's the best email to reach you on?
I'm not allowed to post links yet.
You can check out my email from my github profile.
I couldn't find an email on your GitHub profile. If you're still open to the conversation, feel free to drop me a contact address here or point me to another place to reach you. I'd still love to share the thought.
Oh, sorry.
leekw1245@gmail
You can reach me now
Thanks! I've just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.