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.
IFLogged loss values during training with gradient accumulation are inflated because the loss accumulation is not divided by the number of gradient accumulation steps.
THENModify the `_maybe_log_save_evaluate` method in the Trainer to accept the gradient accumulation steps parameter and divide the accumulated loss by that value before logging. Specifically, change the log line to `logs["loss"] = round(tr_loss_scalar / ga_steps / (self.state.global_step - self._globalstep_last_logged), 4)`, and pass `self.args.gradient_accumulation_steps` (or the number of batches processed) from the training loop.
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