Dataset Optimization: Improve Prompts in Your Dataset
Run automated prompt optimization from the dashboard Optimization tab on any Run Prompt column. Review trial results and copy the winning prompt back into your Run Prompt column.
Optimize prompts directly in your dataset using the dashboard Optimization tab: configure an optimizer, review trial results with before/after comparisons, and copy the winning prompt into your column.
| Time | Difficulty | Package |
|---|---|---|
| 15 min | Beginner | Dashboard only |
- Future AGI account → app.futureagi.com
- A dataset with at least one Run Prompt column (see Step 1 if you don’t have one yet)
Tutorial
Create a dataset with a Run Prompt column
If you already have a dataset with a Run Prompt column, skip to Step 2.
Go to app.futureagi.com → Dataset (left sidebar) → Add Dataset → create a dataset with input columns (for example question, context).
Add a Run Prompt dynamic column:
- Click Add Column → select Run Prompt
- Write a prompt template referencing your input columns, for example:
Answer this question using the context: {{question}} Context: {{context}} - Select a model (for example
gpt-4o-mini) - Run the prompt to generate outputs for all rows
You should see every row filled in with a generated answer under the Run Prompt column. The column stores both the prompt template and the outputs, which is what the optimizer improves.
Tip
See Dynamic Dataset Columns for the full guide on creating Run Prompt columns and other dynamic column types.
Open the Optimization tab
Navigate to your dataset → click the Optimization tab (third tab, after Data and Experiments, before Summary).
You should see the run list for this dataset. If no runs exist yet, an empty state shows a Run Optimization button. Once runs exist, the list view shows an Optimize Prompts button in the header instead.
Configure and launch an optimization run
Click Run Optimization (empty state) or Optimize Prompts (list view header) to open the configuration drawer.
| Field | Value |
|---|---|
| Name | Built from the column name, the optimizer, and a timestamp (for example answer-GEPA-Mar4-1430), edit if needed |
| Choose Column | Select a Run Prompt column from the dropdown |
| Choose Optimizer | Select an optimization algorithm (see table below) |
| Language Model | The LLM used during optimization (for example gpt-4o) |
| Optimizer Config | Parameters specific to the selected optimizer, auto-populated with defaults |
| Evaluations | Select one or more evaluation templates to score candidates |
Available optimizers
| Optimizer | Config parameters | Best for |
|---|---|---|
| Random Search | num_variations | Quick baseline, generates random prompt variants |
| Bayesian Search | min_examples, max_examples, n_trials | Few-shot example selection and ordering |
| ProTeGi | beam_size, num_gradients, errors_per_gradient, prompts_per_gradient, num_rounds | Targeted prompt edits based on error analysis |
| Meta-Prompt | num_rounds | General-purpose prompt rewriting |
| PromptWizard | mutate_rounds, refine_iterations, beam_size | Multi-stage mutation, scoring, and critique-refinement |
| GEPA | max_metric_calls | Evolutionary exploration of diverse prompt styles |
Every optimizer also takes a task_description.
Click Start Optimization to launch the run. You should see the drawer close and a new row appear at the top of the run list with status Pending.
Tip
Not sure which optimizer to pick? Start with Meta-Prompt for general improvement or GEPA for diverse exploration. See Comparing Prompt Optimizers for a hands-on SDK comparison.
Monitor the optimization run
After launching, the Optimization tab shows the run with its current status.
The run moves Pending, Running, Completed; while it’s Running the tab auto-refreshes every 5 seconds. Failed and Cancelled stop it early.
Click the run to see the detail view with a Steps panel showing progress through the optimization stages, a results graph showing score progression across trials, and a trials grid listing each trial’s score and prompt variant.
You should see the status move from Pending to Running to Completed, and the results graph fill in as each trial finishes.
Review trial results and compare prompts
Click any trial in the grid to open the trial detail view. The detail view has two tabs.
The Prompt tab shows a side-by-side comparison: AGENT PROMPT is the baseline prompt from your Run Prompt column, OPTIMIZED AGENT PROMPT is the variant the optimizer generated for this trial. Toggle Show Diff to highlight the changes between the two.
The Trial Items tab shows the individual iterations the optimizer ran to produce this trial’s prompt, with input, output, and evaluation score per row.
Review a few trials to see how different optimization paths produced different prompt structures.
You should see a clear score gap between the best and worst trials, with the diff view showing exactly what changed. For example, the baseline scored 0.61 and the best trial 0.79 (illustrative, from an example run). The best-scoring trial’s prompt is the one you carry back to your column.
Use the optimized prompt
Once you’ve identified the best trial:
- Copy the optimized prompt from the trial detail view
- Paste it over your Run Prompt column’s template, or into a prompt template in Prompt Workbench for version control and production serving
To re-run optimization with different settings, for example a different optimizer or metric, click Optimize Prompts again from the Optimization tab.
You should see the previous run stay in the list, so you can compare its trials against the new run.
Tip
Run the same optimizer with different evaluation metrics to see which metric drives the most useful prompt improvements.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No Run Optimization button on the Optimization tab | The dataset has no Run Prompt column yet | Add and run a Run Prompt column first (Step 1), then reopen the tab |
| Run stays in Pending for a long time | The optimization queue is processing other runs ahead of yours | Wait, the tab auto-refreshes every 5 seconds once the run moves to Running |
| Run shows Failed | An error occurred inside the optimizer or an evaluation step | Open the run’s Steps panel to see where it failed, fix the config, and relaunch |
| Show Diff shows no changes between AGENT PROMPT and OPTIMIZED AGENT PROMPT | The optimizer converged on a variant close to the baseline for that trial | Check other trials in the grid, or increase the trial budget (num_variations, n_trials) and rerun |
| Optimization ran against the wrong data | Choose Column pointed at the wrong Run Prompt column | Cancel the run, relaunch, and confirm the correct column before clicking Start Optimization |
| Optimized prompt didn’t change the dataset outputs | An optimization run never writes back to the Run Prompt column | Manually copy the optimized prompt into the column template, or save it to Prompt Workbench (Step 6) |
Next: Comparing Prompt Optimizers for a hands-on SDK comparison across optimizers.
Questions & Discussion