Detailed Analysis
A systems administrator or IT operations professional has posted to the r/ClaudeAI subreddit describing a manual, repetitive workflow: checking more than 12 distinct internal systems to identify and deprovision users, a process they currently perform approximately 50 times per month against a pool of roughly 300 active users. The core question posed is whether AI agents like Claude represent a viable automation path, or whether purpose-built browser automation frameworks such as Selenium or Playwright are the more appropriate solution for this kind of multi-system identity lifecycle management task.
The practical answer to this question lies largely in the nature of the systems involved. Traditional scripting frameworks like Playwright or Selenium are purpose-engineered for deterministic, repeatable browser interactions — filling form fields, clicking buttons, navigating to known URLs — and are highly reliable when the target interfaces are consistent and well-structured. For a workflow as predictable as "log in, navigate to user section, search by identifier, execute removal," these tools offer speed, precision, and minimal overhead. They also integrate naturally with orchestration layers and can be scheduled, logged, and version-controlled with standard software engineering practices.
AI agents, including those powered by Claude, introduce a different and complementary set of capabilities. Where conventional scripts break when a UI changes or an unexpected modal appears, an AI agent with browser-use capabilities can reason about what it sees on screen and adapt. Claude-based agents are increasingly being deployed in so-called "computer use" or agentic browser contexts, where the model interprets rendered pages and decides how to interact with them — a meaningful advantage when dealing with legacy or inconsistent internal tooling. This distinction matters here because the poster's 12+ systems almost certainly vary in interface design, authentication flows, and search mechanisms, creating exactly the kind of heterogeneous environment where rigid scripts require sustained maintenance.
The broader trend this question reflects is the emerging bifurcation in automation strategy: structured, API-accessible systems benefit most from traditional RPA or scripting approaches, while visually-driven, inconsistent, or legacy interfaces are increasingly being targeted by LLM-powered agents. A hybrid architecture — using Playwright for the well-behaved systems and an AI agent layer for the outliers — is becoming a recognized pattern in enterprise IT automation. Additionally, the tracking requirement the poster mentions (knowing which systems have already been deprovisioned for a given user) points to the need for a lightweight state management layer, whether that is a simple spreadsheet, a database, or a purpose-built identity governance tool, which neither AI agents nor browser scripts provide natively.
The post also surfaces a broader operational risk that the automation question implicitly raises: deprovisioning workflows, if automated without appropriate guardrails, carry meaningful security and compliance implications. Removing a user from the wrong system, failing to confirm successful removal, or running the automation against stale data could create access control gaps or audit failures. Whether the solution employs Claude, Playwright, or a combination, robust logging, confirmation checks, and human-in-the-loop review for edge cases are not optional enhancements — they are foundational requirements for any production-grade identity lifecycle automation system.
Read original article →