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.
IFQuery on MilvusVectorStore with node_ids populated but filters empty (None) causes AttributeError because the code attempts to join list objects in 'expr' with FilterCondition from query.filters, assuming filters is not None.
THENUpdate the query method to handle the case where filters is None. When filters is None or empty, construct the expression using only node_ids if provided. In the MilvusVectorStore.query method, add a guard: if query.filters is None or not query.filters.filters, then only use node_ids to build the filter expression instead of attempting to combine with FilterCondition.
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