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 running vLLM with `--device cpu` on a GPU-compiled vLLM package, inference fails with TypeError due to wrong attention metadata class being used (e.g., XFormersMetadata or FlashAttentionMetadata receiving unexpected keyword argument 'is_prompt').
THENEnsure the vLLM package is compiled for CPU (e.g., install vllm-cpu or build with CPU flags) or explicitly avoid running CPU workloads with a GPU-compiled build. Alternatively, revert to v0.4.2 where this bug was not present. To fix the code, patch `cpu_model_runner.py` to pass only the expected keyword arguments to the attention metadata constructor, removing 'is_prompt' if not supported.
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