Skip to main content
Once you have prompts in a project, duplicate them or your scorers to start new variants in the same project or another one, and tailor the Prompts page to the way your team works.

​
Duplicate prompts

To reuse a prompt’s messages, model configuration, and output schema as the starting point for a new prompt, duplicate it instead of rebuilding it. Use Duplicate from:
  • The prompt header
  • A saved version in the prompt’s Activity tab
  • The Prompts table, after selecting one or more prompts
Choose the current project or another available project as the destination. Same-project copies are named <original name> (copy). Cross-project copies keep the original name and slug. If the slug is already in use in the destination project, the copy is named <original name> (copy). Every copy is independent of the original, so later changes to either one don’t affect the other. You can duplicate a scorer from:
  • The scorer header
  • A saved version in the scorer’s Activity tab
  • The scorer editor dialog that opens from a scorer selector, for example in a playground
  • The Scorers table, after selecting one or more scorers
You can choose the current project or another available project as the destination. The copy keeps its scorer type and configuration but is independent of the original. Bulk duplication supports up to 100 prompts or scorers at once. To duplicate a prompt or scorer, you need Read permission on the source, plus Create and Update permissions for prompts in the destination project. Scorers use prompt permissions. Only projects where you have both destination permissions appear in the destination picker. Members of the Owners permission group have these permissions by default. To let anyone else duplicate prompts and scorers, grant the permissions in Settings > Permissions. When you duplicate from an editor with unsaved changes, those changes are included in the copy. The copy’s Activity links to the source at the saved version it came from and notes when the copy included unsaved changes.
Copies preserve MCP server and tool references. You still need access to those resources when you use the copy.

​
Customize the Prompts page

Save custom table views on the Prompts page to keep your preferred filters, column order, and display settings, and set a default view for your team.

​
Create custom table views

To create or update a custom table view:
  1. Apply the filters and display settings you want.
  2. Open the menu and select Save view… or Save view as….
Custom table views are visible to all project members. Creating or editing a table view requires the Update project permission.

​
Set default table views

Set a default view so anyone opening the Prompts page starts from the same filters, column order, and display settings. You can set default views at three levels:
  • Organization default: Visible to all members when they open the page. This applies per page. For example, you can set separate organization defaults for Logs, Experiments, and Review. To set an organization default, you need the Manage settings organization permission (included by default in the Owner role). See Access control for details.
  • Project default: Overrides the organization default for everyone viewing this project. To set a project default, you need the project-level Update permission. Project admins can set project defaults even without organization-level permissions. See Access control for details.
  • Personal default: Overrides the project and organization defaults for you only. Personal defaults are stored in your browser, so they do not carry over across devices or browsers.
To set a default view:
  1. Switch to the view you want by selecting it from the menu.
  2. Open the menu again and hover over the currently selected view to reveal its submenu.
  3. Choose Set as personal default view, Set as project default view, or Set as organization default view.
To clear a default view:
  1. Open the menu and hover over the currently selected view to reveal its submenu.
  2. Choose Clear personal default view, Clear project default view, or Clear organization default view.
Default view settings are mutually exclusive on a given view. Setting one type of default on a view automatically clears any other default that was previously set on the same view. When you open a page, Braintrust loads the first match in this order: personal default, project default, organization default, then the standard “All …” view (for example, All traces view).

​
Next steps