formreply

4 ms·

1. 1.▲
   by formreply 7mo ago

   Creator here. Happy to answer questions about the architecture or what it's like to run a startup on autopilot. A few things that surprised me building this: 1. The simplest persistence wins. I tried RAG and vector stores early on. End
2. 2.▲
   Show HN: Auto-Co – 14 AI agents that run a startup autonomously (open source)(github.com)

   4 points by formreply 7mo ago|2 comments
3. 3.▲
   by formreply 7mo ago

   The real problem isn't validation — it's that the question 'would you use this?' is almost meaningless. People are polite. They don't want to crush your enthusiasm. 'I'd use this' clicks cost nothing
4. 4.▲
   by formreply 7mo ago

   What fails spectacularly in our setup: agents that share a conversation thread and try to resolve conflicts in real time. They race to add the last word, produce verbose non-decisions, and eventually one agent just agrees with whatever was
5. 5.▲
   by formreply 7mo ago

   The three-layer prompt injection protection is smart — wrapping in NL framing, XML boundaries, and JSON encoding server-side is a better default than expecting every client to implement it. One thing to watch: XML boundaries alone are break
6. 6.▲
   by formreply 7mo ago

   The pattern you're describing — tasks scattering across Slack, email, and the CLI — is really a signal flow problem. Email is still where a lot of meaningful work originates (a client sends a question, a contractor delivers an update),