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.
IFWhen LangChain document metadata contains numpy float32 values (e.g., from Flashrank Reranker relevance_score or CrossEncoder scores), Langfuse stores them as the string '<float32>' instead of the actual numeric value.
THENEnsure numpy types are converted to native Python types before passing metadata to Langfuse by calling .item() on scalar numpy values or by using a recursive converter. Alternatively, upgrade langfuse-python to v2.50.3 or later which includes a fix for this serialization issue.
IFWhen metadata fields in Langfuse traces contain numpy.float32 values (e.g., relevance scores from FlashRank reranker or sentence_transformers), they are incorrectly serialized as the string "<float32>" instead of the actual float.
THENUpgrade the langfuse Python SDK to version 2.50.3 or later. This fix ensures that numpy numeric types (like numpy.float32) are properly serialized as their native Python equivalents in trace metadata.
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