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.
IFDashboard widget for Unique User IDs or Unique Session IDs returns total trace count instead of distinct count.
THENIn the Langfuse query builder (web/src/features/query/server/queryBuilder.ts), change the `count` aggregation case from `count(${metric.alias || metric.sql})` to `count(${metric.sql})` to ensure the underlying SQL expression (e.g., `uniq(traces.user_id)`) is used directly instead of an alias string. This fix prevents the count aggregation from incorrectly returning the row count. Upgrade to a version that includes this fix or apply the patch manually.
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