Pattern preview · 12 of 4,089 sample rules shown · site-specific intelligence stays private
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.
Sample rules shown
1
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
parameter_collision
observability-parameter-collision-when-using-langfuse-s-python-openai-wrapper-and-pa-18a865ac
IFWhen using langfuse's Python OpenAI wrapper and passing `metadata` parameter with `store=True`, the metadata is intercepted by langfuse and not forwarded to OpenAI.
THENTo ensure OpenAI receives the metadata for stored completions, use the native OpenAI client directly for calls requiring `store=True` with metadata, or pass metadata through langfuse's dedicated mechanism (e.g., `langfuse_context` or separate trace parameter) while avoiding the `metadata` key in the chat completion call. Alternatively, modify the langfuse wrapper to use a different parameter name for its own metadata to avoid collision.
Tier 170%
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