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.
IFUsing an Ollama model that includes a 'thinking' field in its streaming responses (e.g., gpt-oss:20b) causes LiteLLM to raise APIConnectionError: Unable to parse ollama chunk
THENIntercept and transform the streaming chunks to remove or normalize the 'thinking' key. This can be done either by creating a custom Ollama Modelfile that overrides the TEMPLATE to suppress 'thinking' output, or by implementing a LiteLLM callback that preprocesses each chunk before parsing. Example: parse the JSON chunk, detect 'thinking', and either delete it or merge its content into a standard field like 'response'.
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