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.
IFUsing MetadataFilters with multiple filters and FilterCondition.OR on Qdrant vector store returns an empty response even though each filter alone returns results.
THENInstead of relying on FilterCondition.OR, perform separate queries for each filter and merge the resulting nodes. Alternatively, check that the vector store's filter implementation correctly handles OR conditions; consider using a single filter with multiple values if applicable.
IFMultiple MetadataFilters with OR condition on Qdrant returns empty response in LlamaIndex v0.9.44.
THENPerform separate queries for each filter and merge the results (e.g., union of node sets). Alternatively, upgrade to a newer version of LlamaIndex that correctly processes OR conditions on Qdrant, or verify that the vector store supports OR logic.
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