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
2
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
device_backend_mismatch
performance-device-backend-misma-running-vllm-inference-on-cpu-e-g-benchmark-throug-1146124a
IFRunning vLLM inference on CPU (e.g., benchmark_throughput --device cpu) fails with TypeError: XFormersMetadata.__init__() got an unexpected keyword argument 'is_prompt'.
THENEnsure that the attention backend selection in get_attn_backend checks the runtime device_type rather than relying on the compiled package variant. Update cpu_model_runner.py to pass the correct arguments to the metadata constructor, aligning with recent refactoring that removed the 'is_prompt' parameter.
Tier 170%
device_backend_mismatch
infrastructure-device-backend-misma-running-vllm-with-device-cpu-causes-typeerror-xfor-e5b30383
IFRunning vLLM with `--device cpu` causes TypeError: XFormersMetadata.__init__() got an unexpected keyword argument 'is_prompt' or similar metadata init error.
THENEnsure the attention backend selection function (`get_attn_backend`) checks the runtime device type (e.g., `device_type` parameter) instead of only relying on the compiled package type. If the package is GPU-compiled but CPU execution is requested, either raise a clear error or fall back to a compatible backend. The fix involves modifying `cpu_model_runner.py` to pass the correct metadata class or adding a compatibility check in the executor factory.
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