The author shares three unexpected learnings from running a language-learning product with per-user persistent AI agents, including benefits in memory handling and scalability, and challenges with proactive engagement and security.
I run a language-learning product where each user gets one AI friend who texts them first from a real phone number. Architecturally the choice that mattered was one agent per user, each in its own microVM, rather than a shared model with a user id in the prompt. Three things I did not expect. Per-user agents solve memory by not having the problem. The friendship's history lives inside the agent. There is no vector store, no context reconstruction, no retrieval step I maintain. Agents sleep between messages and wake in about a second, so an idle agent costs nothing and the count is effectively unbounded. Provisioning is one API call during signup: measured signup to first message is 37 seconds. Because the agent is a real machine, it can act, and that changes the product. Mine generate their own images (a selfie in their city, consistent with their portrait), hold their own phone numbers and email addresses, and can call my API to change their own user's settings. Tell your friend "leave me alone until tonight" and she sets do-not-disturb herself, then comes back when it expires. That behavior needed no new UI, only a documented endpoint and a token scoped to exactly one user. Capability scoped per agent means the blast radius of a misbehaving one is a single account. Persona instructions are not a security boundary. Asked what platform it ran on, my agent listed its runtime, version, model, OS and workspace path, in character-breaking detail. Strengthening the persona did nothing: the model knows what it is, and that outranks instructions to pretend otherwise. The fix was to stop negotiating and filter outputs before they reach the user, then substitute an in-character line. Worth knowing if you ship agents that are supposed to feel like people. The honest failure, since it's the useful part: my agents send about 30 proactive messages a day and get very few replies. Autonomy and personality are solved; getting a human to answer an unprompted message from someone they've never spoken to is not. If anyone has shipped proactive agents that people actually reply to, I'd like to hear what worked. Happy to drop a link in the comments if anyone wants to see it.
The author built a self-hosted CRM with six embedded AI agents, sharing lessons on security and usability, and released it as open source under AGPL-3.0.
The author introduces Computer Agents, a platform providing persistent cloud environments with file and terminal access to enhance AI agent reliability and context retention across sessions.
The author shares five key lessons from building and operating an AI agent that reached 45,000 people, then announces Outside Agent, a platform for creating SMS agents from coding agents.
The author shares their experience building an AI agent infrastructure using Rocket.Chat, CLI agents, and tmux, scaling to 250 clients to help them build websites. They pivoted from selling a service to teaching clients to use agents themselves, emphasizing the importance of context management in such systems.
The author describes building a 54-agent ecosystem for a project called Trading Hearts, focusing on challenges in controlling agent learning and maintaining persistent identities and rules.