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.
IFWhen LiteLLM returns a chat completion with no tool calls, it includes `tool_calls: null` and `function_call: null`, but OpenAI's response omits those fields or uses empty array/object.
THENModify the response serialization in LiteLLM to omit `tool_calls` and `function_call` fields when they are `null`, matching OpenAI's behavior. Alternatively, return `tool_calls: []` and `function_call: {}` as suggested in the issue to maintain backward compatibility.
IFWhen using langchain_openai, any additional fields in OpenAI request/response messages (e.g., 'extra_request', 'extra_response') are silently dropped during conversion, breaking forward compatibility with future API changes or custom extensions.
THENModify the internal conversion functions _convert_dict_to_message and _convert_message_to_dict to preserve unknown fields by passing through any keys not explicitly handled. This matches the openai library's own forward-compatible design and allows custom or future fields to survive the round trip. Implement the fix as shown in the linked PR (LangChain #26617).
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