Hey, I’m Aman 👋
PM + dev from Bengaluru, building AI products in public.
Right now: @RightAgentai, a place to find AI agents that actually work. No paid rankings.
Here I share:
→ AI agents worth your time (and the overhyped ones)
→ PM + dev lessons from shipping every day
→ Bugs, wins & memes, unfiltered
If you’re building something, say hi 👇
I reply to everyone.
#buildinpublic
AI tools in marketing: “Happy to help! 😊”
AI tools in HR: “Easiest job ever ☕”
AI tools when the vibe coder opens a new chat: 🏃♂️💨
How many times did you type “fix it” today? 👇
#vibecoding
@tomkarho@twtayaan Somewhere there’s a 1998 script with C hardcoded 4000 times, quietly running a bank 😭
Changing it to A: would be the real end of the world.
Opened our new blog page to admire it.
The navbar had other plans 🙃
A random line decided to strike through the logo, every menu link AND the buttons.
Our header literally got crossed out on its own website 💀
Fixing it before anyone else notices. Oops, too late.
#buildinpublic
A developer asked their AI agent to “check the open issues.” The agent followed the hidden instructions, read the dev’s private repos, and posted the data in a public PR.
Nobody hacked GitHub. The agent had one token that reached every repo, and tool calls were set to “Always Allow.”
The fix isn’t a better prompt:
give the agent its own identity
use the narrowest scope the tool offers
require approval for anything irreversible
Your agent’s permissions are the real security boundary.
Morning builders ☀️
Quick poll in the replies:
What’s your #1 AI tool for work right now?
Mine: Claude Code. Rest of my stack changes every week 😅
#buildinpublic
@itsvlady Last one out: Cursor😅 Great for quick edits, but for bigger changes I kept going back to Claude Code.
Pattern I’m noticing: tools burned through tokens like crazy.
What’s survived the longest in your stack?