Braintrust

Connect Braintrust when the traces you want to evaluate are already in Braintrust. Tensile reads logs from the selected projects, backfills from the configured date, and continues syncing through its connector. Source identity is retained where the provider supplies it.

Connect one or more projectsCopy Anchor Link

1. In Braintrust, create an API key that can read the projects you intend to connect. Copy the key and the project IDs.
2. In Tensile, open Settings → Integrations → Braintrust and select Connect. Only organization owners and admins can manage connections.
3. Enter the Braintrust Host. For Braintrust cloud, the default is https://api.braintrust.dev; use your configured API URL for a self-hosted instance.
4. Enter the API key and one or more Project ids. Put one project ID per line or separate them with commas.
5. Review the Customer-id metadata key (customer_id by default) and Session-id metadata key (session_id by default). The session key groups spans into a session when present; otherwise Tensile groups from the root span.
6. Set Backfill from to an ISO date to limit the initial history. Leave it blank to request all available history.
7. Select Connect or Update. Connected means the configuration is saved; it does not verify provider access or synchronization.

Select the pencil Edit connection icon before updating a saved connection. Leave the API key field blank to keep the existing key. Keep the key private and grant only the read access required for the projects you selected.

View logs for one projectCopy Anchor Link

On a saved Braintrust connection, select View logs beside a configured project. Tensile opens /settings/integrations/logs?provider=braintrust&project=ID with that project's stored ID. Select a row to read its full-width request detail; the breadcrumb returns to the scoped list, and up/down commands move through the loaded collection. Browser Back retains the source context. Only rows from the selected workspace, Braintrust source and project belong in this view, including filter suggestions and opened payloads. An empty or failed view does not prove that the provider has no logs, that synchronization is complete, or that the saved key still works. The authenticated /raw-logs reader and direct SDK, Pulse and Error Captures links remain available even though Raw Logs is not in main navigation.

To disconnect the saved connector, select the destructive Disconnect icon beside Edit connection in the header. Review the confirmation dialog before confirming. Cancel keeps the saved connection.

Read delivery and processing coverageCopy Anchor Link

The current Settings layout does not show the earlier connector-checkpoint, processing-freshness or full-history register panels. Work identity configures source keys; saving that mapping does not establish source coverage.

A saved connection does not prove that traces arrived, processing completed or history is complete. Those claims require source and stored-processing evidence for the same bounded window. Missing intervals, unknown eligibility, held receipts and failed receipts remain unresolved. A finite scan cannot establish complete history. Ask the workspace's source owner for the relevant retained evidence; there is no coverage verification action in this connection form.

Check project access from a terminalCopy Anchor Link

Load BRAINTRUST_HOST and BRAINTRUST_API_KEY from your approved secret store. Use the same provider host that you enter in Tensile. Replace YOUR_PROJECT_ID with the ID of a project that the key can read.

cat > braintrust-check.json <<'JSON'
{"query":"SELECT id FROM project_logs('YOUR_PROJECT_ID') LIMIT 1","fmt":"json"}
JSON

curl --fail --silent --show-error \
  --request POST "${BRAINTRUST_HOST}/btql" \
  --header "Authorization: Bearer ${BRAINTRUST_API_KEY}" \
  --header "Content-Type: application/json" \
  --data @braintrust-check.json

This read query requests at most one log ID. A successful response checks provider access. An empty result can mean that the project has no logs. It does not save a Tensile connection or prove that Tensile imported any traces. See the Braintrust query reference.

What happens to imported tracesCopy Anchor Link

The connector maps Braintrust trace/span records into Tensile sessions and events. Some recorded Braintrust identity and timing fields support grouping and case provenance. Availability depends on the source data; Tensile does not infer that a case came from Braintrust merely because it belongs to a particular customer.

Connecting projects makes eligible trace evidence available to the configured workspace. It does not approve a pack or activate evaluator-pack scoring. Draft pack review, calibration, sealed validation, and owner approval are separate steps. See Evaluator packs.