Concepts
The ideas behind AFKmate and why it works the way it does.
Passive Code Review
Code reviewers exist. Passive code reviewers? AFKmate is the first. Instead of you going to the AI, the AI comes to you. It waits for you to step away, reviews your code while your mind is resting, and has findings ready when you get back. No context switch. No copy-pasting into a chat window. Just your code, reviewed.
This matters because the alternative is reactive. Something breaks, you paste the error into ChatGPT, get an answer, paste it back. Every time you do that, you lose flow. You lose the mental model you spent twenty minutes building. AFKmate removes that entire loop.
Issue Types
The kind of bugs that don't make your IDE scream red but wait until your users find them:
- Errors: Silent syntax errors, off-by-one bugs, null references, logic mistakes that produce wrong results
- Security: Unsanitized input, hardcoded credentials, missing authentication, injection vulnerabilities
- Warnings: Unused variables, unreachable code, deprecated APIs, shadowed names
- Suggestions: Performance traps, readability improvements, best practices
Local vs Cloud Analysis
Your code, your choice:
- Cloud: More accurate, larger models. Requires internet. Code processed in memory only, never stored.
- Local: Full privacy. No cloud, no external servers, no trust required. Works offline. No usage limits.
Switch between them anytime. No lock-in.
Next: Reference