AI tool comparison
AI Subroutines vs Goose
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Automation
AI Subroutines
Record a browser task once, replay it 500x at zero token cost
75%
Panel ship
—
Community
Free
Entry
AI Subroutines from rtrvr.ai are a new automation primitive: you record a browser task once (a form submission, a LinkedIn connection, a CRM update), and that recording becomes a deterministic, callable tool that AI agents can invoke with different parameters — without spending tokens on every run. Unlike Playwright, Browser-Use, or other out-of-process solutions, Subroutines execute entirely inside your browser tab, inheriting your live session cookies, CSRF tokens, and signed headers automatically. The technical approach is clever. During recording, the system captures network requests and DOM interactions, then ranks captured requests to identify the actual API call (filtering out analytics and telemetry). Replay-hostile identifiers are stripped while stable endpoints are preserved. The result is a script that runs in your browser context — no session rebuilding, no key extraction, no proxy rotation needed. The AI handles parameter selection; the script handles execution. The business case is clear for outreach and operations teams: bulk LinkedIn campaigns, CRM mass-updates, scraping pipelines, and form submissions that would cost hundreds of tokens per run instead execute as cheap deterministic scripts. The model positions Subroutines as the "function call" layer beneath AI agents — the actions that don't need intelligence every time they fire.
AI Agents
Goose
Block's local-first AI agent with native MCP support, runs on your machine
75%
Panel ship
—
Community
Paid
Entry
Goose is Block's open-source local-first AI agent, built with native Model Context Protocol (MCP) support from the ground up. Unlike cloud-based agent platforms, Goose runs entirely on the developer's machine — connecting to local MCP servers, reading files, running shell commands, and integrating with local services without sending data to third-party infrastructure. The agent supports multiple LLM backends (Anthropic, OpenAI, local Ollama models) and exposes a plugin-style architecture where capabilities are added as MCP servers. This means any developer can extend Goose with custom tools — a database connector, a local calendar integration, a custom code execution environment — without modifying the core agent. The design reflects Block's privacy-first engineering culture. Goose has been growing steadily in the developer community, particularly among engineers at companies with strict data security requirements who want agent capabilities without cloud data exposure. The local-first + MCP-native combination is genuinely differentiated — most agent platforms either require cloud APIs or bolt MCP on as an afterthought rather than building around it.
Reviewer scorecard
“The 'record once, replay many' pattern solves a real cost problem in agent pipelines. The in-browser execution model is clever — you get auth context for free instead of fighting with session management. This is the kind of tool that drops into existing workflows without requiring a rewrite.”
“The MCP-native architecture is the right bet for 2026. Instead of each agent building its own tool integration layer, the ecosystem converges on MCP servers as the universal extension mechanism. Goose being built around this from day one means it ages better than competitors who bolted MCP on later.”
“Browser automation that runs inside your session is exactly the attack surface that malicious sites exploit. Subroutines executing in-tab with full cookie access means a compromised script could do real damage. The 'zero token cost' claim also obscures that you still need LLM calls for parameter selection — the savings are real but overstated.”
“Running locally is a privacy win but also means you're responsible for setup, updates, and debugging when things break. For teams without a dedicated platform engineer, the operational overhead of a local-first agent is real. Also, Goose's cloud connectivity features (for collaboration) create the same privacy exposure it's trying to avoid.”
“This is the 'compilation' step for agentic workflows — moving from 'LLM decides every click' to 'LLM selects a pre-compiled action.' That separation of concerns (intelligence vs. execution) is how you scale agent operations from one-off demos to production pipelines. The pattern will be widely copied.”
“Block building a local-first agent is a quiet but important data point: large companies are hedging against cloud AI dependency. As MCP becomes the standard protocol for AI tool connectivity, agents that natively speak MCP will have massive ecosystem advantages over those that need adapters.”
“For creators doing outreach, social posting, or newsletter campaigns, this is genuinely transformative. Recording a campaign action once and letting AI handle personalization at scale is the efficiency unlock that makes solo creator businesses actually viable at volume.”
“For creators who work with sensitive client material — brand assets, unreleased campaigns, personal client data — the local-first guarantee removes the biggest barrier to using AI agents professionally. I can let Goose read my project files without wondering if they'll appear in someone's training data.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.