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 using a ReAct agent with the hwchase17/react prompt, the LLM (e.g., Llama3) produces a response containing both an Action and a Final Answer in the same turn, causing ReActSingleInputOutputParser to raise OutputParserException.
THENModify the output parser to handle ambiguous outputs: check for the presence of Final Answer first and return it if found, otherwise parse Action. Alternatively, enforce stricter prompting in the template to instruct the model to never include both (e.g., 'If you have the final answer, output only Final Answer and nothing else'). A custom parser that splits on known delimiters can also be used.
IFValueError: Could not parse LLM output when using HuggingFaceHub or Bloom models with conversational-react-description agent.
THENSwitch to an LLM that reliably outputs the required format, such as OpenAI, or customize the agent prompt to include explicit format instructions (e.g., 'Action:', 'Action Input:'). Alternatively, use a different agent type like 'zero-shot-react-description' that may tolerate less structured output.
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