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
2
Categories
2258
Tier-1 (public)
4,089
Tier-2 (your patterns)
private to your site
sse_timeout
mcp-sse-timeout-sse-connection-from-a-client-e-g-cursor-drops-with-d60163d8
IFSSE connection from a client (e.g., Cursor) drops with 'TypeError: terminated: Body Timeout Error' after approximately 300 seconds (5 minutes) of inactivity, causing tool calls to fail.
THENImplement a keep-alive mechanism by periodically writing an SSE comment (e.g., `res.write(': keepalive\n\n')`) to the HTTP response stream. Set an interval (e.g., every 25-30 seconds) to send this comment, preventing the connection from being closed due to inactivity. This keeps the SSE stream alive until a real event (tool result, notification) is sent.
Tier 170%
sse_timeout
mcp-sse-timeout-sse-connection-from-mcp-server-to-client-cursor-ti-015db008
IFSSE connection from MCP server to client (Cursor) times out after 5 minutes with 'Body Timeout Error'.
THENImplement a keep-alive mechanism by periodically writing a comment line ': keepalive\n\n' to the SSE response stream. Set an interval (e.g., 25 seconds) to write this comment before the client's timeout threshold (typically 5 minutes). This prevents the connection from being considered idle and terminated.
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