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 using Anthropic reasoning models (e.g., claude-haiku-4-5-20251001) with 'thinking' enabled, the LLM response contains a content array with objects of type 'thinking' and 'text', which Langfuse's generation parser fails to handle.
THENModify the response extraction logic to iterate over the content array, concatenate all 'text' blocks into the assistant message, and optionally capture 'thinking' blocks as a separate field. Ensure the parser can handle 'thinking', 'text', 'tool_use', and 'tool_result' block types without breaking experiments or evaluators. This fix enables correct logging of reasoning models' outputs.
IFWhen using an LLM integration (like LiteLLM) with response_format='json_object' on Ollama, the response parser crashes with KeyError: 'name' because it assumes all JSON responses contain a function call.
THENModify the response transformation to check for the presence of a tool_call or function_call key before accessing its fields. If absent, treat the response content as direct JSON text. This prevents false errors when the model outputs only a JSON object without a function call wrapper.
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