We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFClient call_tool hangs when receiving invalid JSONRPCMessage via SSE due to truncated payload causing JSON parsing failure.
THENEnsure that errors during SSE event processing are correctly propagated to the client. Validate JSON before parsing and handle exceptions by sending an error response message that the client can interpret, rather than sending the exception object. Implement a retry mechanism or timeout to prevent client from hanging indefinitely.
IFClient hangs indefinitely when server sends truncated JSONRPCMessage in SSE event due to special characters like \x85 causing JSON parse failure, and exception is not propagated to client.
THENAdd a custom message_handler to the ClientSession that listens for ValidationError and cancels the task group to break the hang. Implement an exception_handler that calls session._task_group.cancel_scope.cancel() on ValidationError, and pass it via the message_handler parameter of ClientSession.
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site