About AFKmate
A passive AI code reviewer for developers who treat coding as a craft.
Why AFKmate exists
Coding is an art. The elegance of a well-named function, the satisfaction of a clean abstraction, the discipline of handling edge cases because you respect the craft. That's the kind of development we believe in.
But the world is moving fast. Vibe coding, prompt-driven development, copy-paste from ChatGPT. These shortcuts work for throwaway scripts, but they don't work for software you actually care about. Software that handles real users' data, runs in production at 3 AM, and gets maintained by someone else six months from now.
AFKmate was built for developers who still write their own code. Who still read their diffs before pushing. Who believe the craft of building software is worth doing right.
What AFKmate is
AFKmate is the world's first passive AI code reviewer. A VS Code extension that detects when you step away from your keyboard, analyzes your open files while you're gone, and has actionable findings waiting when you get back.
Not another autocomplete tool. Not another chatbot. AFKmate doesn't write code for you. It reviews the code you've already written, with depth and care, and surfaces the things you might have missed: silent syntax errors, small logic bugs, security oversights, performance traps.
Code reviewers exist. Passive code reviewers? AFKmate is the first.
What we believe
Coding is a craft. We build for developers who care about every line they ship. AFKmate respects that you're the developer, your code is your responsibility.
Privacy by default. Your code is yours. Run everything locally through Ollama. No cloud, no external servers, no trust required.
Work while you rest. No buttons to click, no commands to run. AFKmate detects idle time and reviews your code automatically, so findings are ready when you return.
Signal, not noise. Every finding includes a confidence level. No spam, no obvious suggestions. Only the things that actually matter for your code.
The problem we solve
There's a gap in every developer's workflow. You write code, you test it, maybe you push it through CI, and you move on. But between writing and testing, subtle issues hide. The off-by-one error, the unsanitized input, the O(n²) loop that compiles fine but scales terribly.
Most developers don't have a teammate reviewing every line. And you can't just go to ChatGPT every time something breaks. That's reactive. You're already broken, already context-switching, already losing flow.
AFKmate flips this. Instead of you going to the AI after something breaks, the AI comes to you before it breaks. While you're away. While your mind is resting. Your code gets a second pair of eyes, even when nobody else is around.
Get in touch
Have questions, feedback, or want to talk about how you write code? We'd love to hear from you.