AI Subroutines: Deterministic Browser Automation with Zero Token Cost

What AI Subroutines Do
AI Subroutines record browser tasks once and save them as callable tools that replay at zero token cost, zero LLM inference delay, and with 100% determinism. The generated script executes inside the webpage itself, not through a proxy, headless worker, or out-of-process solution.
Key Architectural Decision
The script executes inside the webpage's execution context, which means all authentication, CSRF tokens, TLS sessions, and signed headers get added to requests automatically. No certificate installation, TLS fingerprint modification, or separate auth stack maintenance is required.
Recording Mechanism
During recording, the extension intercepts network requests using two layers:
- MAIN-world fetch/XHR patch installed before any page script runs
- Chrome's webRequest API as a correlated fallback for CORS and service-worker paths
Request bodies including FormData, Blob, and raw bytes are captured, not just JSON.
Network Capture Processing
The system scores and trims approximately 300 requests down to about 5 based on multiple signals:
- First-party vs. third-party origin (+20 / −15)
- Known telemetry hosts (Sentry, Segment, Hotjar, RUM): −80
- Temporal correlation to DOM events (+28 within 800ms, +16 within 2.5s)
- Method and payload shape (mutating POST/PUT/PATCH/DELETE: +35; GET: +5; with request body: +8)
- Response quality (2xx: +12; 4xx+: −25; non-empty body: +4)
- Volatile operation identifiers (−18) for GraphQL queryId, doc_id, operationHash
Volatile GraphQL operation IDs trigger a DOM-only fallback before they break silently on the next run.
Generated Code Structure
The generated code combines network calls with DOM actions (click, type, find) in the same function via an rtrvr.* helper namespace. The top five ranked requests plus DOM interactions get rendered into a 12,000-character context for the generator.
Usage Pattern
Point an AI agent at a spreadsheet of 500 rows, and with just one LLM call, parameters are assigned and 500 Subroutines are kicked off.
Key Use Cases
- Record sending an Instagram DM, then have a reusable routine to send DMs at zero token cost
- Create a routine to get latest products in a site catalog, call it to get thousands of products via direct GraphQL queries
- Set up a routine to file EHR forms based on parameters, with AI inferring parameters from current page context
- Reuse routines daily to sync outbound messages on LinkedIn/Slack/Gmail to a CRM using an MCP server
Why This Matters
The fundamental problem with browser agents for repetitive tasks is that going through the inference loop is unnecessary. Recording once and having the LLM generate a script that leverages all possible interaction methods (direct API calls, DOM interactions, third-party tools/APIs/MCP servers) provides deterministic, cost-effective automation.
📖 Read the full source: HN LLM Tools
👀 See Also

Local MCP Server Connects Claude to Mac Apps Without Cloud or Tokens
Local MCP is a native macOS MCP server that gives Claude Desktop, Cursor, Windsurf, and VS Code access to Mail, Calendar, Teams, and OneDrive data on your Mac without cloud processing or API tokens.

Custom Status Line for Claude Code Shows Context Usage, Cost, and Git Branch
A Reddit user created a bash script that leverages Claude Code's statusLine setting to display real-time information including context window usage, session cost, active model, and current git branch. The script requires jq and is available on GitHub.

Custom Output Styles Collection for Claude Code
A developer has created 13 custom output styles for Claude Code that modify the AI's behavior through system prompts. The styles include Roast for brutal code critique, Socratic for guided questioning, Breaker for adversarial testing, Ship It for pragmatic solutions, Paranoid for security focus, and TDD for test-driven development.

OpenClaw Codex-GPT5.4 Task Validation Loop Issue
A developer reports Codex-GPT5.4 through OpenClaw gets stuck in a task validation loop during autonomous project work, repeatedly identifying and confirming tasks without executing them. They've implemented workspace controls including TASKS.md, heartbeat rules, and persona files to address the issue.