AI Subroutines vs Hippo Memory

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.

Hippo Memory is an open-source Python library that implements a memory system for AI agents inspired by how the human hippocampus encodes, consolidates, and retrieves episodic memory. Instead of naive vector-store RAG (embed everything, retrieve top-k), Hippo Memory models three distinct memory processes: rapid binding (short-term working memory for the current session), consolidation (background thread that compresses and indexes memories during agent "sleep" cycles), and pattern completion (retrieval that reconstructs partial memories from minimal cues). The practical upshot is an agent memory layer that degrades gracefully over time — important memories persist and get reinforced, while irrelevant details are naturally compressed away. The library exposes a clean Python API: agents call memory.encode(event) to store experiences and memory.recall(cue) to retrieve them, with Hippo handling the underlying consolidation pipeline. It supports multiple backends: in-memory (for testing), SQLite (local), and ChromaDB/Qdrant (production vector stores). This is a solo indie project from a developer who spent months researching neuroscience memory models before coding, and it shows — the architecture is notably more thoughtful than the typical "LLM + Pinecone" memory bolt-on. The Show HN launch attracted substantive discussion about the trade-offs vs. simpler RAG approaches, and several researchers noted similarities to recent cognitive science work on predictive coding in hippocampal circuits.