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.
IFCustom headers set in SSEClientTransport configuration are not sent in the initial GET /sse request.
THENModify the `_startOrAuth` method to merge the custom headers from `this._requestInit?.headers` into the request used for the SSE connection, mirroring how `send()` already handles headers for POST requests to /messages.
IFCustom headers set in SSEClientTransport options are not passed to the initial /sse endpoint request.
THENApply the fix from PR #318 that merges this._requestInit.headers into the fetch options for the initial SSE connection. Ensure that headers from the requestInit are forwarded to the /sse call by including them in the fetch options.
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