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.
IFTimeout errors occur when fetching traces with specific filters (tags, timestamp) from a large ClickHouse-based project due to inefficient subqueries and lack of time range constraints.
THENAlways provide both fromTimestamp and toTimestamp parameters in API calls to the traces endpoint to constrain the data scanned by ClickHouse, significantly reducing query time. Additionally, ensure that project_id, trace_id, and tags columns are indexed to optimize joins.
IFDatabase timeout error when fetching traces with tags and timestamp filter, especially on large projects.
THENAlways provide both `fromTimestamp` and `toTimestamp` parameters when querying traces to enable efficient index usage. Also ensure proper indexing on `project_id`, `trace_id`, and `tags` columns. Consider breaking complex subqueries into simpler steps if timeout persists.
IFTimeout error when fetching traces with filters on large projects.
THENProvide both fromTimestamp and toTimestamp parameters to limit the time range, reducing the query complexity and preventing timeouts.
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