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.
IFAutoGPT only supports gpt-4 via hardcoded model in call_ai_function, preventing use of other/local LLMs.
THENModify call_ai_function to read a chosen model from a config file (e.g., config.ini) and use conditional logic to call different AI APIs based on the model value. Replace the hardcoded model with a config-driven approach to support multiple backends.
IFLlamaCpp with Llama 3 model produces nonsensical output when context length exceeds 4k.
THENSet `rope_freq_base=500000` in the LlamaCpp constructor or via `model_kwargs` to override LangChain's default hardcoded RoPE frequency base. Ensure the parameter is passed directly to llama.cpp, as LangChain's defaults (rope_freq_scale=1.0, rope_freq_base=10000) may override model metadata. For custom context sizes, recalculate the appropriate rope parameters.
IFThe AI agent only supports a single LLM provider by default, restricting user choice for local or alternative models.
THENImplement a configuration file (e.g., config.ini) with a model selection flag. Modify the AI calling function to read this flag and use conditional logic to invoke the appropriate API (OpenAI, local, etc.). Default to a common model if the flag is missing. This decouples model selection from code and allows easy switching.
IFError 'Failed to get supported params: argument of type 'NoneType' is not iterable' appears when using crewAI with an LLM provider.
THENEnsure the model parameter is specified in the 'provider/model-name' format (e.g., 'groq/llama3-8b-8192') to match litellm's expected naming convention. This resolves the NoneType iteration error.
IFWhen using OpenAI GPT-5 chat model (gpt-5-chat-latest) via LiteLLM, setting temperature to a value other than 1 causes UnsupportedParamsError.
THENSet litellm.drop_params=True to drop the unsupported temperature parameter, or use temperature=1. The allowed_openai_params workaround may not override this restriction; dropping unsupported params is the reliable fix.
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