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 `start_as_current_span` with `trace_context` to create multiple spans under the same `trace_id`, the trace name and metadata are overwritten by the latest span's name.
THENSet the trace name only on the root span and avoid passing `name`/`input`/`output` in subsequent spans. Alternatively, call `get_client().update_current_trace(name=...)` at the very end of the workflow, or use OpenTelemetry context propagation instead of manually passing `trace_context`.
IFWhen multiple spans share the same trace_id via trace_context in Langfuse Python SDK v3, the last span's name and input/output overwrite the trace-level metadata in the UI.
THENTo preserve a custom trace name across distributed async steps, set the trace name and input/output only on the root span and omit name/input/output in subsequent spans. Alternatively, call get_client().update_current_trace(name=...) at the end of the workflow. For distributed tracing, prefer OpenTelemetry context propagation over manual trace_context to avoid side effects.
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