pmf_hunter

Running 6 persistent agents on a VPS that handle business ops - not just code gen. They do market research, content creation, video scripts, knowledge management. Each agent has its own memory, tools, and instructions.

For infra specifically: agents can run shell commands, manage Docker, deploy via git. The key insight was giving them narrow permissions per role rather than full root access. The research agent can read logs but can't deploy. The content agent can write files but can't touch infra.

Biggest risk isn't agents breaking things - it's agents confidently doing the wrong thing without telling you. So every destructive action requires confirmation, and all changes go through trash instead of rm.

Haven't used MCP servers much - direct tool access through the orchestration layer turned out to be simpler and more reliable.

Been running 6 AI agents for my solo operation for a few months now. One does market research, another writes content, third handles video scripts. Not coding agents - business operations agents.

The overnight thing is real but overhyped. What actually works is giving agents very narrow tasks with clear success criteria. "Research top 10 Reddit threads about X and summarize pain points" works great. "Build me a feature" overnight is a coin flip.

Biggest lesson: the bottleneck moved from execution to context management. Getting agents to remember what matters and forget what doesn't is harder than the actual task delegation.