Our #neatHack submission
TenantGuard: an AI security agent that catches its own bad fixes. It patches a vuln, and if that breaks real users, it reverts & retries until tests pass.
Live 👉 https://t.co/Ja6gA7HHZW
Built with @arithecfo@EntireHQ@neatlogs
https://t.co/eRu9JpPhv3
AI code-fixers ship broken patches — pass the security test, silently break real users.
TenantGuard catches its own bad fixes, reverts & retries until the tests pass.
Live 👉 https://t.co/Ja6gA7HHZW
@EntireHQ@neatlogs@arithecfo#neathack
Most AI code-fixers ship broken patches -if pass the security test but silently break real users, and nobody checks.
TenantGuard fixes the bug, catches its own bad fix, reverts, and retries — proven by tests, not vibes.
Live 👉https://t.co/Ja6gA7HHZW
Built for #neatHack@neatlogs
3/ Running live on Claude Opus 4.6 (AWS Bedrock) → traced in @neatlogs, coding sessions checkpointed in @entire, unit economics (~$0.005/fix) modeled in https://t.co/QYXKnajvR4 AI LONE STAR. Code + demo: https://t.co/D1z7wVzpvl #neatHack
Building TenantGuard for #neatHack — a security agent you’d trust to run unattended.
Tenant A could read Tenant B’s invoices. It reproduces the leak, writes a fix — then catches its OWN fix breaking legitimate access, reverts,
Verified by tests, not vibes.
2/ The hard part isn’t fixing the bug — it’s not shipping a fix that breaks legitimate same-tenant access.
A deterministic verifier demands BOTH:
✅ cross-tenant reads blocked (403)
✅ legitimate access still works
Naive agents fail this. TenantGuard recovers.
@LuxProgram Hi! I'm Madhan. I build AI agents and ship them live.
Open to remote work.
Portfolio: https://t.co/ADFiPxqAaD
GitHub: https://t.co/o78VFOXulQ
@gkcs_ Building applications, in these AI era, isn't great, but how it will be impacted, Or how it will be used , reporting Potholes is there's , does it solves the problem, like do they patch all under certain period of time?....