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 CondensePlusContextChatEngine retrieves zero document nodes, it returns the hardcoded string 'Empty Response' instead of allowing the LLM to respond naturally.
THENModify the chat engine to not short-circuit on empty retrieval. Instead, pass an empty context to the LLM and let it generate a response based on its training and system prompt, or use a default context. Override the `chat` method to check for empty nodes and still invoke the LLM with a fallback context.
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