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
3
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
environment_variables
infrastructure-environment-variable-when-using-os-environ-variable-name-in-litellm-con-7f312de3
IFWhen using os.environ/VARIABLE_NAME in LiteLLM config.yaml for model_list, model is not recognized and litellm.BadRequestError is returned.
THENEnsure the .env file is in the same directory as the docker-compose.yml file. Verify environment variables are present inside the container with `docker exec <container> env`. Avoid quotes or comments in .env as Docker's --env-file may not parse them correctly. If issues persist, hardcode the values as a workaround.
Tier 170%
environment_variables
ai-agents-environment-variable-when-using-ollama-as-llm-provider-a-keyerror-key-n-a91d7a91
IFWhen using Ollama as LLM provider, a 'KeyError: key_name' occurs during crew initialization because the 'ollama' entry in ENV_VARS lacks a 'key_name' for 'API_BASE'.
THENAdd an entry for 'ollama' in the ENV_VARS dictionary with a key_name for 'API_BASE'. The workaround is to import ENV_VARS from crewai.cli.constants and update it with the required mapping before importing the crew. Ensure the .env file includes API_BASE=http://site_1:11434.
Tier 170%
environment_variables
infrastructure-environment-variable-using-openai-package-1-x-x-with-azure-openai-in-la-3b956ecc
IFUsing openai package 1.x.x with Azure OpenAI in LangChain causes ValidationError 'base_url and azure_endpoint are mutually exclusive' when both OPENAI_* and AZURE_* environment variables are set simultaneously.
THENEnsure only AZURE_* environment variables (AZURE_OPENAI_ENDPOINT, AZURE_OPENAI_API_KEY) are set. Unset or leave undefined any OPENAI_* variables such as OPENAI_API_BASE, OPENAI_API_KEY, OPENAI_API_TYPE, or OPENAI_API_VERSION. This avoids the conflict where LangChain's AzureChatOpenAI attempts to pass both base_url (from OPENAI_API_BASE) and azure_endpoint (from AZURE_OPENAI_ENDPOINT) to the OpenAI client.
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