I currently do not automatically detect the agents themselves, and most of the bot traffic is ignored, but for the traffic that is not ignored it usually shows as a 0s session (so you can filter for all sessions that have a 0s replay, which are usually bots).
I am still torn whether I should actually track bots/AI traffic or simply drop it, maybe I will add a toggle in the setting, maybe it's at least interesting to see how much spam the website gets and coming from where.
Oh, and as for the agents themselves browsing the website, if the agent uses an actual browser with JS enabled (like headless puppeteer), then you would actually be able to see how the agent browsed the website.
That's a good start I'd say, but I agree with you that detection is not trivial. I wonder if there's enough value in distinguishing between AI agents (with full browser) and humans. What use cases would it enable?
For the distinguishing part, it's hard to tell if it can be done anyway, as the agent browsers are still new and constantly changing, and it's up to them if they will correctly identify themselves or not (same as with crawler/bots, the main indication is still the source IP address).
There could be use cases, like tracking if your content was stolen/parsed by an AI, maybe future pay-per-request for LLMs, etc.
I am still torn whether I should actually track bots/AI traffic or simply drop it, maybe I will add a toggle in the setting, maybe it's at least interesting to see how much spam the website gets and coming from where.