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 LiteLLM /v1/responses with Bedrock Claude, sending the assistant tool call block (with the same toolUseId) together with the tool result causes a ValidationException due to duplicate toolUseId.
THENIn the response transformation logic, before reattaching cached tool calls from TOOL_CALLS_CACHE, check if the incoming payload already contains an assistant block with a matching tool_call_id. If found, skip the cache reattachment to avoid duplication. This prevents the Bedrock rejection.
IFWhen using LiteLLM's /responses endpoint with Claude on Bedrock, if the client resends the assistant tool-call block (same toolUseId) together with the tool result, LiteLLM attaches a cached duplicate causing a ValidationException for duplicate Ids.
THENUpgrade LiteLLM to a version containing the fix (nightly after PR merge). The fix detects when the incoming payload already includes a matching assistant tool-call (same role and tool_call_id) and skips the cache-based reattachment, preventing duplicate toolUseId blocks.
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