How do I know? Because I’ve done it.

Blackboard published a post late in 2025 which concluded (emphasis is mine):

AI Agents don’t show up as separate apps or users—they look identical to normal student activity in the LMS. Because they operate at the web interaction and automation layers—filling in forms, clicking buttons, making API calls, etc.—they fall outside what the LMS itself can control. Many are completely invisible to the platform.

It is true that current/standard LMS log data that Blackboard collects cannot differentiate between users. This is as true for Student A and Student B as it is for Student A and Agent A. In fact, this is why we built Cursive (ensuring the right student is the learner is an essential foundation for assessment validity).

But this is untrue when log data are expanded. This plugin expands log data locally to capture and finger print users using their browser and page interaction data (mouse movements, key presses, clicks), and identifies AI-mitigated access to your LMS by systems and agents like OpenClaw and it's derivatives.  

1. All data remains local (no API required)
2. User sessions are not impacted
3. Thresholds can be set by an administrator

Note:

1. for operational security, the best version of this plugin is not available for download so please contact us for the best and latest version. 
2. a paid, more robust version of this plugin is available that covers AI extensions, agents, and more: contact us.  
3. this plugin can be part of a set, including an Authentication and Text Editor plugin which can be used to take automatic actions against Agents on the LMS.
4. if you intend to use this to protect integrity of an examination please consider alternative/additional means (proctoring, in class exams, lockdown browsers).