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.
IFAzure AI Search vector store throws KeyError when 'metadata' field is absent in the search index.
THENMake the metadata field name configurable (e.g., via environment variable AZURESEARCH_FIELDS_TAG) or allow multiple metadata fields instead of hardcoding a single 'metadata' field. Remove the assumption that a 'metadata' field exists; handle missing fields gracefully or let users specify field mappings.
IFQdrantVectorStore's _collection_exists method catches unexpected responses (HTTP 500, timeout) and returns False, causing recreate_collection to delete existing data.
THENFix _collection_exists to distinguish genuine non-existence (e.g., 404) from errors. Re-raise unexpected exceptions or use create_collection when collection status is uncertain to prevent data loss.
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