I shipped six agents inside a self-hosted CRM instead of a chat window. Here's what that changed
Summary
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.
Similar Articles
AI Dashboard + Infrastructure + Rocket.Chat
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.
I gave every user their own persistent agent instead of one shared chatbot. Three things I learned running it in production
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.
gave my agent its own email inbox, things i'd do differently
A practitioner shares lessons learned from running an AI agent with its own email inbox — dedicated address, own domain for reputation, draft-only mode to guard against prompt injection, signed webhooks, and human-accessible inboxes — after Grok Bot shipped similar functionality.
I built a local workspace where agents work inside custom apps you build, not just chats
Second is an open-source tool that lets developers build custom GUIs for teams of AI agents, enabling deep async work within tailored apps instead of just chats.
11 agents running autonomously running my full trading system.
A maker describes a multi-agent system built over six months for trading research and preparation, where 11 agents research, score, stage, and report while the human retains final trade execution. The author shares lessons learned and offers GitHub repo access via their Substack.