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
project_name_conflict
observability-project-name-conflic-when-using-opik-evaluation-evaluate-with-track-pro-0420258b
IFWhen using opik.evaluation.evaluate with @track(project_name='...') on inner functions, data logs to Default Project and a warning appears about nested span project name 'None' being used instead.
THENSet the project name in the experiment_config parameter of the evaluate() function rather than (or in addition to) the @track decorator. For example: opik.evaluation.evaluate(..., experiment_config={'project_name': 'your_project'}). This ensures the evaluation context uses the correct project name.
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