Skip to content
Tech News
← Back to articles

My Agent Setup

read original more articles
Why This Matters

This article highlights the innovative approach of using autonomous agents to streamline product and nonprofit management, reducing the need for extensive staffing. It demonstrates how tailored AI agents can handle diverse tasks, from administration to technical maintenance, paving the way for scalable, efficient operations in the tech industry.

Key Takeaways

My agent setup

(this was written by a human. I had my gtm-agent review and make some changes, but I then mostly reversed all of those taking me 10x more time than had I just shipped it with missing commas, run-on sentences, and 6 instead of six. Refer to "Has it been worth it?" at the end.)

A few people have asked about my agent setup, but first let me talk about the goal. I'm working on a few products as well as a nonprofit. The only product I've mentioned so far is The Daily FM, which is just something I wanted so I built it.

The goal of all this agent experimentation is to scale multiple products and the nonprofit with fewer staff and volunteers than would otherwise be needed. In short, I'm creating a staff of agents. I'm about a month into this charade, so it's still early days.

I know the leading influencers in the space are yelling into their mics about thousands of agents (what happened to swarms?), self-improving loops (or is it graphs?), etc., but before getting to thousands, I'd like to start with a modest six.

The agents

Profiles

ea-agent: My executive admin. It's basically there to remind me of stuff, interact with my calendar, and manage work in Linear like a program manager. ops-agent: Monitors site performance and Sentry, makes sure stuff keeps running, and triages issues. It either fixes them, assigns them to dev-agent, or sends them to me. dev-agent: My core developer, with GitHub access to a few projects. gtm-agent: My marketer. It looks at funnels, traffic numbers, and social media, and has skills for writing and social media management. research-agent: Searches the web, does long asynchronous research, and builds reports. vps-agent: My infrastructure manager, with root access to the agent box. It can create new agents, add MCP servers and skills, and handle server maintenance. It only responds to me in Buzz.

Runtime and memory

All the agents are currently Hermes agents, but I predict this will change at some point. They are defined by SOUL.md , AGENTS.md , skills, tools, MCP servers, a Mnemosyne memory bank per profile, and a shared Obsidian wiki synced to my machine. In theory this is all portable. It's just a few easily-locatable 1's and 0's. Right? RIGHT?

... continue reading