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.
IFLlama 3 produces nonsensical output when context length exceeds ~4k tokens via LangChain's LlamaCpp wrapper.
THENSet the `rope_freq_base` parameter directly in the LlamaCpp constructor to 500000 (for default 8192 context) instead of relying on model_kwargs. For custom context sizes, recalculate based on RoPE scaling. This overrides LangChain's hardcoded default of 10000, which is incompatible with Llama 3's architecture.
IFWhen using vLLM with temperature=0 and top_p=1.0, batch inference may produce empty responses with no generated tokens.
THENTo avoid empty outputs, set a small non-zero temperature like 1e-3 or 1e-2 instead of exactly 0. Alternatively, implement a min_tokens parameter in the vLLM sampling configuration or add post-processing to detect and retry empty generations.
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