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 using langfuse_otel callback with litellm, nested OpenTelemetry traces (e.g., a decorated @observe function containing a litellm.completion call) are not properly nested; they appear as separate traces.
THENCreate a child span using langfuse_client.start_span() and pass the parent's otel span as metadata key 'litellm_parent_otel_span' to the completion call. Example: subspan = langfuse_client.start_span(name='litellm_generation_span'); completion(..., metadata={'litellm_parent_otel_span': supspan._otel_span}). This forces litellm to use the parent span context.
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