Detailed Analysis
A Reddit user posting to r/ClaudeAI raises a practical question about leveraging AI agents — specifically tools with web crawling and interface-traversal capabilities, referred to as "Cowork" and "openclaw" (likely informal or autocorrected references to agentic AI tools built on models like Claude) — to automatically generate end-user documentation for a SaaS application. The poster uses a generic CRM product analogous to Zoho as the illustrative use case, and proposes a workflow where an AI agent crawls the live application, follows button clicks and user flows, and uses the existing code repository documentation as a structural scaffold to infer intent and dependencies. The poster openly acknowledges starting from zero experience with this class of agentic tooling and is seeking community input on both methodology and output format, explicitly framing the exercise as a learning experience rather than a production requirement.
The question touches on a genuinely emerging use case for large language model agents: automated documentation generation from live software interfaces. The proposed approach — combining web/UI traversal with codebase context — reflects an intuitive but non-trivial workflow. Effective SaaS documentation requires not just identifying UI elements but understanding task-oriented user flows, which demands that the agent correlate visual navigation paths with underlying functional logic. Code repository documentation can supply the "why" behind features, but the agent must bridge that to the "how" as experienced by a non-technical end user. Whether current agentic tools can reliably perform this synthesis at the quality level required for publishable documentation remains an open question that the post implicitly surfaces.
The mention of screenshots as a desirable documentation component highlights a key technical constraint. Static text generation is well within current LLM capability, but capturing and annotating screenshots requires either computer-use functionality (where the agent operates a real browser session and captures screen state) or integration with dedicated screenshot APIs. Claude's computer use feature, available through Anthropic's API, is one mechanism that enables this kind of visual capture during agentic traversal, though it requires deliberate setup and is not available as a default plugin in most consumer-facing interfaces. The poster's uncertainty about whether plugins are needed reflects the fragmented tooling landscape around agentic workflows, where capability boundaries are still poorly documented for newcomers.
This post fits into a broader trend of practitioners attempting to use AI agents to automate traditionally labor-intensive technical writing tasks. Documentation is notoriously difficult to keep current in fast-moving SaaS products, and the appeal of an agent that can re-crawl an application after each release and regenerate updated guides is significant. Companies like Mintlify, GitBook, and Readme.io have begun integrating AI-assisted writing into their documentation platforms, but fully autonomous generation from UI traversal rather than from manually authored content remains largely experimental. The community interest in Claude-based approaches specifically suggests that developers are treating the model's strong instruction-following and long-context capabilities as potential advantages for maintaining coherent, structured documentation across complex multi-screen workflows.
The poster's openness to any output format — wiki, static HTML, or otherwise — is practically significant because format choice has downstream implications for maintainability and version control. Markdown-based outputs compatible with tools like MkDocs or Docusaurus tend to be most amenable to iterative AI-assisted updates, since they are diffable, Git-friendly, and re-renderable without manual reformatting. If the goal is a repeatable, agentic documentation pipeline rather than a one-time artifact, the choice of a plain-text structured format is likely to matter considerably more than the poster's current framing suggests, and represents one of the more substantive design decisions any practitioner building such a system would need to resolve early.
Read original article →