Before you start
Patterns runs Loop against your project on a schedule, so two things need to be in place first:- A way to pay for inference. Patterns runs on Loop’s GPT-5.6 models. By default these are Braintrust’s built-in models, which draw down your organization’s monthly model credits and need no setup. On the Starter plan, they require at least one organization owner with a work email address, or a payment method on file. See Requirements. To run Patterns on your own key, or to keep it running once your credits are exhausted, configure an OpenAI-compatible AI provider for your organization or project.
- Permission to create automations in the project. Members of the Owners and Engineers permission groups have this by default. Enable patterns is shown to everyone, so without permission you’ll see an error when you click it rather than a hidden button.
Enable pattern discovery
- Go to Patterns and click Enable patterns. Once Patterns is on, this button becomes Settings.
- In the Introducing Patterns dialog, optionally choose a Slack workspace and channel to be notified in when Loop finds patterns.
- Click Enable patterns to confirm.
If a project has no patterns yet and no run is in progress, click Analyze patterns to queue another run without waiting for the schedule.
Tune the automation
The default automation is an ordinary Loop automation, so you can change its instruction, schedule, model, query range, and destinations at any time. To edit it, either click Settings on the Patterns page and select the automation, or go to Settings > Automations. The fields worth revisiting first:- Frequency. How often the run happens. A project with steady traffic rarely needs more than daily.
- Default query range. How much recent data each run inspects. Each run inspects the full range, not only the traces created since the previous run, so a wide range costs more.
- Instruction. What Loop should look at, how deeply, and when to stop.
- Destinations. Where run digests are delivered.
Keep the instruction framed around finding or updating patterns, even when you narrow the automation to one concern. An instruction that asks for a summary produces a summary, not a pattern record.
Add a focused automation
You can run several pattern automations alongside the default one. Use a focused automation when one concern needs its own scope or schedule: tool-call errors, cost growth, latency for a specific set of customers, or quality regressions. To add one, select Settings > New automation on the Patterns page. Braintrust opens a prefilled automation for you to review and save. All of them write into the same patterns list.Common issues
A run finished but recorded nothing
A run finished but recorded nothing
Loop records a pattern only when it can attach supporting evidence, so a quiet run is a normal outcome rather than a failure.To work out what happened, open the automation, select the Past runs tab, and select the run to read the transcript. Select Continue to fork it into an editable thread and ask Loop directly why it recorded nothing.If runs are consistently empty, the query range or the instruction is usually too narrow.
Patterns aren't notifying Slack
Patterns aren't notifying Slack
Destinations belong to automation runs. Patterns that Loop records during an interactive chat appear in the list but do not trigger Slack or webhook destinations.Confirm the destination is configured on the automation itself, under Destinations in the configuration panel, and that the Slack workspace is still connected.
The page asks you to upgrade your data plane
The page asks you to upgrade your data plane
Patterns requires data plane v2.13 or later. To upgrade, see the routine upgrade guide.
Next steps
- Review and act on patterns once the first run finishes.
- Run Loop on a schedule to configure destinations, write permissions, and past runs in depth.
- Set up alerts for conditions you already know how to detect.
- Active observability for coding agents to find recurring problems in coding-agent sessions with Topics facets and a Loop automation.