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.
IFAttempting to resume LoRA training with wandb logging results in a ConfigError due to changing 'model/num_parameters' from 0 to actual count.
THENBefore resuming, set environment variables WANDB_RESUME='allow' and WANDB_RUN_ID to the previous run ID. Additionally, ensure the wandb config allows value changes by passing allow_val_change=True when initializing the run, or create a custom callback that skips logging num_parameters during resumption. A simpler workaround is to set the wandb config's 'allow_val_change' parameter to True in the wandb.init call.
IFResuming LoRA training with wandb logging causes a ConfigError due to attempt to change config key 'model/num_parameters' from 0 to a non-zero value.
THENApply the fix from PR #33464 which ensures the wandb config is initialized correctly before logging parameter count. Alternatively, manually set allow_val_change=True on the wandb config object before resume, or set the environment variables WANDB_RESUME='allow' and WANDB_RUN_ID to the same run ID as the previous run.
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