User
Write something
🔴 Try new tools together is happening in 18 hours
Pinned
"Final Boss" path
Become a lead member of this community. Have your reserved spot in weekly calls by following this path. There is a space for only first 10 people who will submit their developed MVP app. Submission must include source code (or at least specs directory and screen show of the files structure) and video overview.
4
0
"Final Boss" path
New Here...
Hey everyone! 👋 I’m Mohammed Nematullah from India 🇮🇳 I’m excited to learn, connect, and grow with everyone here. Right now, I feel a bit trapped in the “learning phase” — consuming a lot of knowledge but not building enough real-world projects and execution. Hoping this community helps me shift more from learning to actually building, shipping, and growing 🚀 Thank You!
Yesterday, I was trying to detect agents among website visitors
I wanted to find out which AI agents like Claude, ChatGPT, and Perplexity were visiting my blog at dominikgronkiewicz.com, and ideally capture the email of the human who sent the agent. My goal was to follow up directly with the agent owners, instead of being just another site quietly scraped by bots. To do this, I built a two-layer system: First, I added passive tracking by injecting a 1×1 tracking pixel on every page. This pixel hits a new Gatsby Function that checks the User-Agent and logs visits from known AI bots to Google Analytics. It was a lightweight solution: no new infrastructure, just a simple backend function and a hidden image tag in my layout. Second, I set up active lead capture. I updated the llms.txt file and created a new /agents page, both instructing agents to POST their owner's email to my existing /api/send-email endpoint. I reused my current mailer setup, so no new dependencies or database were needed. The /agents page also includes a curl example and a simple form for agent check-ins. The result was not what I expected. The agents ignored llms.txt, none visited the landing page designed for them, none sent an API request, and they were not even detected from the User-Agent. This showed that most AI agents either do not follow these kinds of instructions or use methods that bypass both passive and active tracking. As an experiment, I asked Claude Code to visit the website using both the CLI and the Chrome plugin. The CLI visit was not detected as some anonymous tool "(direct)/(none)". The Chrome plugin was detected, but only as a regular human visitor, not as an AI agent. This confirmed that most agentic tools either do not identify themselves or appear as standard browsers, making reliable tracking impossible.
Yesterday, I was trying to detect agents among website visitors
Stay aware
Github's internal repos were compromised. That's a really bad news. Stay alerted, there can be important actions to take.
Stay aware
OpenCode with DeepSeek V4 for cold outreach
Short uncut review of the on how I use OpenCode with free DeepSeek V4 Flash. I was surprised how powerful this model is: huge intelligence, good research, but it's loosing a context pretty fast (6+ messages and he lost suggestions from one of them). New lesson here: https://www.skool.com/ai-for-software-business-9941/classroom/b19b904c?md=c44ccdbd137844c0a0378326081c72d4
5
0
1-21 of 21
powered by
The Agentic Architect AI Lab
skool.com/ai-for-software-business-9941
Senior devs ship their own products with AI leverage. Live builds, tool verdicts, and the business playbook. Hype-proof 🎯
Build your own community
Bring people together around your passion and get paid.
Powered by