Introducing operate.txt: A YAML spec for AI agents navigating SaaS products
A developer has created operate.txt, a specification for documenting how AI agents should interact with web applications. The file addresses issues encountered when using Claude's computer use feature to navigate a SaaS product, where the AI agent repeatedly questioned whether loading screens indicated broken functionality.
Problem and solution
While using Claude Code + computer use to navigate BrandyBee (a SaaS product) as a first-time user, the developer identified specific pain points where Claude struggled:
- During a brand analysis that takes 90-120 seconds, Claude asked "Is this a loading state or is something wrong?" at 28% completion
- An "Approve" button that triggers paid API calls without confirmation UI
- A Language dropdown that only populates after Country is selected
- Async processes taking 2-5 minutes that appear stalled
Each time, the response was "no, that's normal, just wait." This led to the creation of operate.txt as an equivalent to robots.txt for crawlers or sitemap.xml for search engines, but specifically for AI agents operating products.
operate.txt specification
The operate.txt file is a YAML file hosted at yourdomain.com/operate.txt that documents:
- What each screen is
- What loading states look like and how long they take
- Which actions are irreversible
- The step-by-step path for common tasks
- What agents should never do
The most useful section is async_actions, which tells agents details like "this process takes 90-120 seconds, don't refresh, don't navigate away, here are the stages it goes through."
Creation process and examples
The developer open-sourced the spec with real examples including their own SaaS, an e-commerce template, and a SaaS dashboard template at https://github.com/serdem1/operate.txt.
The creation process involves having Claude navigate your product, watching where it hesitates, then having Claude draft the operate.txt file. The developer corrects what Claude gets wrong, creating a feedback loop where the AI finds gaps and the human fills them.
📖 Read the full source: r/ClaudeAI
👀 See Also
Memorine: A Local Memory System for OpenClaw Agents Using Python and SQLite
Memorine is a local memory system for OpenClaw agents that uses only Python and SQLite, with no external dependencies, API calls, or telemetry. It provides fact storage with full-text search, memory decay, contradiction detection, causal event chaining, and optional semantic search via fastembed and sqlite-vec.
ClawCodex /advisor Mode: Pair Cheap Worker with Expensive Reviewer to Cut Costs Without Losing Quality
Open-source Python coding agent ClawCodex adds an /advisor mode that pairs a cheap worker model (e.g., Haiku) with an expensive reviewer (e.g., Opus) at decision points, cutting costs several-fold without sacrificing architectural judgment.
Spectral: Capture App Traffic to Generate MCP Servers for OpenClaw Agents
Spectral is an open-source tool that captures traffic from any application, analyzes it with an LLM, and generates a working MCP server, allowing OpenClaw agents to call the app's real API directly instead of relying on browser automation.
Benchmark shows AI browser automation tools vary 2.6x in token costs despite identical accuracy
A benchmark of 4 CLI browser automation tools using Claude Sonnet 4.6 on 6 real-world tasks found all achieved 100% accuracy, but openbrowser-ai used 36,010 tokens while others used 77,123-94,130 tokens. Tool call count was the strongest predictor of token cost.