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.
IFChatOllama from langchain_ollama does not accept a base_url parameter, defaulting to site_1 and causing connection refused.
THENSet the OLLAMA_HOST environment variable to the Ollama server URL before importing langchain_ollama. If the server is behind a proxy (e.g., Open Web UI), ensure the variable points to the root Ollama endpoint (e.g., http://host:port) without a subpath. Alternatively, use langchain_community.llms.ollama.Ollama which supports a base_url parameter.
IFUsing ChatOllama from langchain_ollama with a remote Ollama server (non-site_1) results in connection refused because there is no base_url parameter.
THENSet the environment variable OLLAMA_HOST to the remote server URL (e.g., http://<host>:11434) before importing langchain_ollama. Ensure this is done before any import statements because the underlying ollama client initializes at import time.
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