Pattern preview · 12 of 4,089 sample rules shown · site-specific intelligence stays private
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.
Sample rules shown
4
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
api_compatibility
ai-agents-api-compatibility-when-using-codex-cli-via-litellm-proxy-with-the-gp-cb849260
IFWhen using Codex CLI via LiteLLM proxy with the gpt-5-codex model, requests fail with a 400 Bad Request error: 'Missing required parameter: 'tools[0].name'. This indicates tool definitions are not properly structured in the forwarded request.
THENVerify that the Codex CLI or any client sending tool calls includes a 'name' field for each tool. If using LiteLLM proxy, ensure it does not strip or alter tool definitions. Upgrade LiteLLM to the latest version and, if needed, switch to the gpt-5 model.
Tier 170%
api_compatibility
mcp-api-compatibility-gitlab-mcp-server-fails-to-validate-project-api-re-408da164
IFGitLab MCP server fails to validate project API responses because the schema expects a 'fork' boolean field that the GitLab API does not always include.
THENMake the 'fork' and 'owner' fields optional in the GitLabRepositorySchema using `.optional()` or remove them if not required. This prevents validation errors when the API response omits those fields, which can happen for non-fork projects or self-managed instances.
Tier 170%
api_compatibility
observability-api-compatibility-when-litellm-is-used-with-a-newer-version-of-the-o-9948e7f8
IFWhen litellm is used with a newer version of the OpenAI Python client (e.g., >1.61.0), it throws AttributeError: __annotations__ in model_param_helper.py when trying to access TranscriptionCreateParams.__annotations__.
THENModify the `_get_litellm_supported_transcription_kwargs` method in `model_param_helper.py` to handle the absence of `__annotations__` by catching `AttributeError` and returning a fallback set of base transcription parameters. Alternatively, use `typing.get_type_hints()` or inspect `TranscriptionCreateParams` fields through a documented API. This prevents the cascade that causes `standard_logging_object is None` and repeated router callback errors.
Tier 170%
api_compatibility
infrastructure-api-compatibility-when-using-litellm-proxy-with-an-openai-compatible-43709b03
IFWhen using LiteLLM proxy with an OpenAI-compatible model that is not registered in LiteLLM's model mapping, the Responses API (v1/responses) returns a 404 error while the Chat Completions API works.
THENRegister the model in LiteLLM's model_prices_and_context_window.json file to enable Responses API support. Alternatively, use the Chat Completions API (/v1/chat/completions) as a fallback until the model is mapped.
Tier 170%
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