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
3
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
azure_ad_auth
security-azure-ad-auth-azure-ad-authentication-fails-with-502-bad-gateway-1c36841f
IFAzure AD authentication fails with 502 Bad Gateway when the Azure account has a profile picture.
THENDisable profile picture retrieval from Azure AD or handle the base64 image data gracefully in the authentication callback. Removing the stored image value in the users table resolves the issue temporarily. Consider configuring the Azure AD provider to not request profile picture or truncate image fields.
Tier 170%
azure_ad_auth
security-azure-ad-auth-azure-ad-sign-in-fails-with-502-bad-gateway-error--36e7eecb
IFAzure AD sign-in fails with 502 Bad Gateway error when the user's Azure account has a profile picture.
THENModify the authentication callback to handle base64-encoded image data from Azure AD. Either truncate the image to a safe maximum size, convert it to a URL if possible, or omit the image from the user session if it causes database storage issues. Check NextAuth.js Azure AD provider documentation for default 48x48 size.
Tier 170%
azure_ad_auth
infrastructure-azure-ad-auth-azure-ad-sign-in-fails-with-502-bad-gateway-error--22fd71ab
IFAzure AD sign-in fails with 502 Bad Gateway error when the Azure account has a profile picture.
THENIf encountering a 502 error during Azure AD sign-in in a self-hosted Langfuse deployment, check the users table in PostgreSQL and delete the value in the 'image' column for the affected user. This workaround removes the problematic profile picture data that causes the authentication callback to fail.
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