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.
IFOpenAI Python package version 1.1.1 breaks LangChain due to changes in error handling imports and client initialization.
THENDowngrade the openai package to version 0.28.1 by running 'pip install openai==0.28.1' or pin 'openai<1.0.0' in requirements until LangChain releases a compatible update.
IFlitellm logging fails with AttributeError: __annotations__ when using openai>=1.62 due to missing __annotations__ on TranscriptionCreateParams.
THENPin openai to version 1.61.0 to avoid the bug, or apply a code fix in model_param_helper.py: replace the call to TranscriptionCreateParams.__annotations__.keys() with a try-except returning a fallback set of transcription parameters, or use a hardcoded list of known optional params.
IFWhen using litellm.completion() with model 'gpt-5-mini' or 'gpt-5' and passing the `n` parameter (e.g., n=1), a BadRequestError occurs because the `n` parameter is incorrectly mapped to 'previous_response_id' in the completion-to-response conversion logic.
THENUpgrade LiteLLM to the latest version where the PR that introduced this mapping was reverted. If an upgrade is not possible, temporarily set `litellm.model_cost['gpt-5-mini']['mode']='completions'` to bypass the response API conversion and use the older completions endpoint.
IFWhen using LangChain's ChatOpenAI, additional fields in request messages (e.g., extra_request) or response messages (e.g., extra_response) are silently dropped by _convert_message_to_dict and _convert_dict_to_message, breaking forward compatibility with new OpenAI API fields.
THENModify _convert_message_to_dict and _convert_dict_to_message in langchain_openai/chat_models/base.py to pass through any fields not explicitly handled. Use the dict representation of the message object and preserve unknown keys. For response messages, ensure extra fields are stored in additional_kwargs or response_metadata.
IFLiteLLM returns null for tool_calls and function_call in assistant messages without tool usage, breaking downstream site_1 that expect empty array and object per OpenAI spec.
THENModify LiteLLM's response serialization to emit an empty array [] for tool_calls and an empty object {} for function_call instead of null when no tools are invoked. This ensures compatibility with LangChain's AgentExecutor and n8n's AI Agent node.
IFLangChain's ChatOpenAI message conversion functions drop extra fields from request and response messages, breaking forward compatibility with OpenAI API extensions.
THENModify _convert_dict_to_message and _convert_message_to_dict in langchain_openai to preserve all extra fields beyond the defined schema, mirroring the openai library's forward-compatible design. This allows new API fields or custom extensions to pass through without being silently discarded.
IFUsing langchain with openai>=1.0 raises AttributeError: module 'openai' has no attribute 'Completion'
THENPin openai version to 0.28.1 in your requirements file or installation command until langchain is updated to support openai v1.0+. For example, use `pip install openai==0.28.1`.
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