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 streaming tool calls from AWS Bedrock Claude with tools that have empty arguments (e.g., no required properties), the tool call index in the final chunk may be incorrect (e.g., 1 instead of 0), causing downstream consumers like LangChain to interpret a single tool call as two distinct calls.
THENIn the Bedrock invoke handler, replace usage of `chunk_data["contentBlockIndex"]` with a dedicated `self.tool_calls_index` counter when appending empty arguments (`"{}"`). This ensures that all chunks belonging to the same tool call receive the same index, even when argument content is interleaved with other content 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