Checking an overnight eval
Dan Fletcher, ML engineer at BigCo, asked whether last night's eval regressed. Memtro summarised the experiment against its baseline, showing which scores fell and how many cases regressed.
Did last night's eval regress, and which production answers scored low?
Braintrust connects Memtro to your LLM evaluations. It reads experiments with average scores and how they moved against a baseline, a project's recent logs with inputs and outputs cut to 300 characters, and projects and dataset names, never dataset rows. When asked, and once an administrator has granted them by name, it can comment on events, create projects, experiments, datasets, prompts, scores and tags, add examples or log events, and run a saved prompt or scorer, which spends model tokens. Deleting a project or experiment is permanent, and saving a prompt version can change what production sends.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Braintrust tool, reads what it needs, and answers with the source cited.
These tools change something in Braintrust. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Braintrust is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Did last night's eval regress?
Show recent low-scoring answers in the support bot project.
How did cost and tokens move in the latest experiment against its baseline?
Add these three failed support answers to the refunds dataset with the expected replies.
Add a comment to that log event saying retrieval missed the refunds policy.
Dan Fletcher, ML engineer at BigCo, asked whether last night's eval regressed. Memtro summarised the experiment against its baseline, showing which scores fell and how many cases regressed.
Sarah Chen, AI product lead at Northwind, asked for today's low-scoring answers, then asked Memtro to add three of them to the refunds dataset with the replies she wrote. Memtro added the three examples, and every later eval run on that dataset used them.
The teams that lean on Braintrust most, a question each of them asks, and what they connect beside it.
A record in Braintrust is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In braintrust.dev, open Settings → API keys as a dedicated user. The key has no scopes and acts as that user, so give the user read access to the projects Memtro should see, and more only for the actions an administrator will grant.
Create a key named for Memtro and copy it, as it is shown once.
In Memtro, open Connections → Braintrust, paste the API key, and set Data plane region to eu if your organisation uses it.
Ask: did last night's eval regress?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Braintrust tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to a logged or experiment event; create a project; rename a project or change its description; delete a project with everything in it; create an experiment, linked to a dataset or baseline; rename an experiment or change its description, tags, baseline or dataset; delete an experiment and its results; create a dataset; add examples to a dataset; write events into a project's logs; save a chat prompt, or a new version of one, under a slug; run a saved prompt, scorer or tool on an input, spending model tokens; add a slider, categorical or free-form review score to a project; add a tag to a project; delete a dataset. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key and optional data plane region. In braintrust.dev, open Settings → API keys as a dedicated user. The key has no scopes and acts as that user, so give the user read access to the projects Memtro should see, and more only for the actions an administrator will grant.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time