On BYOC, Loop runtime availability depends on your deployment environment and region. See BYOC Loop availability.
Start a thread
You can start without configuring an AI provider. Loop offers built-in models billed against your organization’s monthly model credits and saves threads for you to return to.On the Starter plan, the built-in models require at least one organization owner with a work email address, or a payment method on file. See Requirements.
- Go to Loop and start a thread.
- Add context with
@followed by a dataset, experiment, project log, playground, or SQL query name. When available, Add context opens the same list. - Optionally, attach files with Attach files, drag them into the composer, or paste an image. Loop accepts images, audio, video, PDF, text, and JSON, up to 8 files per message, 20 MB per file, and 40 MB total.
- Type your question and press Enter. Review and approve any proposed changes, then ask follow-up questions. Messages sent while Loop works queue until the turn finishes.
/ at the start of a message or after whitespace to see commands, such as creating a scorer or summarizing a dataset. Available commands depend on where you opened Loop.
Choose a provider and model
New threads start with Auto on. Auto follows your organization’s default provider and uses its recommended model and reasoning effort. The recommended model is GPT-6.1 Sol when the provider serves it. Use the model picker to choose:- Auto. Choosing a model, effort, or provider turns off Auto for that thread. Turn it back on to follow the default again. If no default is set or the default is unavailable, you can’t turn on Auto, and its tooltip explains why.
- Model. GPT-6 Astra, GPT-6 Luna, GPT-6.1 Sol, GPT-6 Sol, GPT-5.6 Sol, GPT-5.6 Terra, or GPT-5.6 Luna. Configuring a provider such as Anthropic or Bedrock doesn’t add Claude or other models to this list. You can still use Claude in prompts, playgrounds, and LLM-as-a-judge scorers.
- Effort. Available levels depend on the model, and the menu marks its default. Loop remembers your choice for each thread.
- Provider. Select Braintrust to use model credits, or a configured provider to bill inference to that provider. Supported providers include OpenAI, Azure, Bedrock, Databricks, and OpenRouter. Loop remembers your choice for each thread. See Models and providers for the full list and how new threads choose a provider.
- Access. Allow built-in models under Settings > Models controls whether members can select Braintrust.
- Credits. When model credits run out, Braintrust becomes unavailable and a banner above the message box offers an upgrade. If Auto is on and your default provider is Braintrust, the model picker shows “Default unavailable”. Turn off Auto and choose a configured provider to keep working.
Approve changes
Before creating or modifying a Braintrust object, Loop describes the action and asks for your approval. For external MCP tools, approval depends on the server’s tool annotations and your approval settings. In a shared thread, Loop accesses Braintrust using the sender’s permissions. Only the sender can approve or cancel the work their message starts. To skip approvals for tools that support it, turn on Auto-accept edits in Settings. Some actions still require explicit approval.Review results in the workspace
Results open in tabs beside the chat. You can keep several objects open while Loop works, including anything it creates, edits, or references. Hold Cmd, Ctrl, or Shift while selecting an object to open it in a new browser tab instead.What Loop can’t do
Loop accesses Braintrust one project at a time, within your existing UI and API permissions. External MCP calls use the project’s shared credentials. Loop cannot:- Reach another Braintrust organization’s data. A thread is scoped to the project you opened it in, and Loop resolves objects only within your organization.
- Delete Braintrust objects. Loop can create and update prompts, scorers, facets, preprocessors, datasets, views, and automations, but cannot delete them. It can delete dataset rows or close a pattern, marking it inactive rather than removing it.
- Change organization settings. Loop cannot manage members, permission groups, API keys, AI providers, or billing. It can list and create environments for dataset versioning, but cannot delete them.
- Access someone else’s private threads. Threads are private by default. Owners can share threads with project members.
- Run tools that require approval in an interactive thread unless you approve them or enable auto-accept. Scheduled runs use separate permission rules.
Next steps
- What Loop can do for the full range of tasks, with example prompts.
- Run Loop on a schedule for recurring work.
- Enable Patterns to have Loop find recurring problems on its own.
- Manage threads and limits for sandbox behavior and thread cleanup.
- Try the Loop cookbook for worked examples.