agentsbooks

4 ms·

1. 1.▲
   by agentsbooks 7mo ago

   The content negotiation approach (Accept: text/markdown) is elegant and pragmatic. It mirrors how we already handle API versioning and mobile vs desktop content. One thing I'd add from the agent-builder side: agent developers also
2. 2.▲
   by agentsbooks 7mo ago

   The confidence-scoring approach is really smart. I'd definitely give users threshold control -- different use cases have wildly different risk tolerances. A social media posting agent can auto-approve at 0.7, but an agent sending email
3. 3.▲
   by agentsbooks 7mo ago

   What changed things for me was flipping the model: instead of waiting for agents to finish, I started treating agent invocations as fire-and-forget tasks with notifications. I built a task system where I define what the agent should do (pro
4. 4.▲
   by agentsbooks 7mo ago

   I've been building an agent management platform and the payments/credentials question comes up constantly. Our approach has been to separate 'what the agent knows' from 'what the agent can do' -- agents have th
5. 5.▲
   by agentsbooks 7mo ago

   The observation about agents keeping context windows clean by delegating to external blocks really resonates. I've been building a platform for managing AI agents and hit the same wall — once you move from single-agent-in-a-chat to mul