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 create_tool_calling_agent with an InputChat model that includes ToolMessage in the Union type for chat_history, and the chat history contains messages without 'tool_call_id' (e.g., HumanMessage), a KeyError occurs during pydantic validation.
THENEither remove the specific type hints from the chat_history field (use `List` without Union) or apply a custom validator. The root cause is in the ToolMessage validator expecting 'tool_call_id' unconditionally; a fix is to change `values["tool_call_id"]` to `values.get("tool_call_id")` in langchain_core/messages/tool.py. Updating the library is also recommended.
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