Lindy Teammate: Flo Crivello on Multiplayer Agents, Memory & Why He'd Ban the Chinese Models He Uses

What It Covers

Flo Crivello, CEO of Lindy, details the launch of Lindy Teammate, an AI employee embedded in Slack, while explaining the technical architecture behind multiplayer agent memory, context management using recursive tree structures, caching strategies achieving 85% hit rates, open-source model economics favoring DeepSeek, and his controversial position that Chinese AI models should be banned in the United States.

Key Questions Answered

• •Recursive Context Buckets: Lindy built a centary tree structure (100 children per node) for managing agent memory, enabling access to 10,000 context buckets containing 200,000 tokens each within just two LLM calls — roughly 2 billion tokens total. This solves the compaction problem where standard summarization loses ground truth. Teams should implement self-balancing tree structures rather than naive Russian-doll context chains to avoid O(n) retrieval costs.
• •Caching as Core Economics: Lindy maintains an 85% cache hit rate, and the difference between 85% and 65% nearly doubles inference costs. Any system prompt change can silently break caching. To preserve cache across validator sub-agents, Lindy includes the validator action in the main agent's toolset but instructs it not to invoke it — allowing the validator to inherit the full cached context window without invalidating it.
• •Agentic Memory Over RAG: Rather than retrieval-augmented generation, Lindy uses a memory agent that runs every 15 minutes, logs all queries and retrieval hop counts, then restructures its own memory during idle cycles to reduce hops for frequently asked questions. This self-optimizing librarian approach outperforms static RAG because the agent learns which data sources are noise — automatically ignoring Slack log channels after first exposure.
• •Token Compression Techniques: Two underused compression methods can cut token costs 20–30% each. "Caveman" rewrites memory files in stripped-down syntax, reducing tokens while preserving information — though it harms enterprise auditability. TOON (Token-Oriented Object Notation) replaces JSON as the agent-action data format and measurably improves agent performance, likely because JSON's structural noise outweighs its training-set familiarity advantage. YAML offers similar benefits.
• •Single-Agent Architecture Preference: Division of labor is not a valid reason to use multi-agent systems for AI, unlike human organizations constrained by time and cognitive limits. Agents can fork, duplicate, and parallelize without coordination overhead. Multi-agent systems are justified primarily for security isolation — separating customer-facing agents from internal agents holding repository access, API keys, and financial permissions — not for functional specialization.
• •Vendor Stack for Agent Infrastructure: Lindy recommends buying infrastructure rather than building it. Mesa provides a Git-backed agent-native file system that handles merge conflicts when parallel memory sub-agents write simultaneously. E2B supplies sandboxes. Browser Base handles browser automation. Lindy built its own eval and observability platform only because no adequate solution existed in 2022 — one engineer now maintains it full-time, which Crivello considers excessive given current alternatives.
• •The Centaur Phase Is Temporary: Currently, the best outputs at Lindy emerge from human-AI iteration rather than either alone — matching the historical chess pattern where human-plus-AI briefly outperformed AI alone. However, that gap is narrowing. Crivello expects humans will eventually introduce net noise into optimized AI systems, as occurred in chess. The actionable implication: build AI-native organizational structures now rather than mapping AI onto existing human role hierarchies.