Skip to main content
Anything you can describe, the agent can do on your account: create a benchmark, run models on it, find out why they scored what they did, fix it, train a better model and keep every version in your own repository. It answers in your language and asks before it changes anything.
The BenchGen AI agent's home screen with suggested prompts and a question typed in

The BenchGen AI agent in the platform chat

How to use the BenchGen AI agent

1

Open the chat

Click New Chat in the left sidebar. The BenchGen AI agent is the default agent.
2

Ask in your own words, or paste a prompt

Write what you want as you would to a colleague, or copy one of the prompts below with the button in its top right corner. Words in [brackets] are yours to replace.
3

Confirm what it shows you

Before it creates, spends or changes anything, the agent shows a preview or a plan. Reply yes to go ahead, or say what to change.

Start here

Three prompts that show you what the agent can do in under a minute. See what you have. Your benchmarks, runs, models, training jobs and credits in one answer.
Your first benchmark. A small multiple choice benchmark with a preview before anything is created.
What can you do? A short tour of the agent’s skills, with an example for each.

Create a benchmark

Describe what you want to measure. The agent writes the questions, shows them with the answers, and creates the benchmark as a draft only when you say so. How it works. Multiple choice. The most common kind, balanced answers included.
Open answers. Free text answers, scored on the key points they must contain.
Number answers. Maths or data questions where only the final number counts.
Tool calling. Test whether an agent picks the right tool with the right arguments.
In another language. The agent writes, previews and reports in the language you ask in.
A large benchmark. Written in parts, checked for duplicates, submitted as one.
From an open benchmark. GSM8K, MMLU, TriviaQA or any Hugging Face dataset, licence checked and source credited.
One MMLU subject. Multiple choice, the choices in their original order.
From your repository. A benchmark folder in your GitHub or GitLab, public or private.

Run and compare models

A run needs a published benchmark. The agent says which model it picked and gives you a link. How it works. Publish and run. Both steps in one message.
Compare models. The same benchmark on several models, side by side.
Check on a run. State, score and what to do next.
Pick a model. Find a model in the catalogue before you spend credits.

Understand the results

Read only: these prompts never change anything. How it works. Why that score? The wrong answers, and the reason for each.
Review a benchmark. Everything that looks wrong with it, with evidence.
Hardest questions. Which questions separate strong models from weak ones.
Compare two runs. What got better and what got worse, question by question.
Look at the raw answers. The prompt the model saw and exactly what it replied.

Fix a benchmark

A low score often means the answer key is too narrow, not that the model is weak. The agent proves a fix on answers it already has before offering it. The full story. Find and prove a fix. No model is called, nothing is changed yet.
Apply it and measure again. The fix, then a fresh run of the same model.
Edit a question. One change, checked first.
Change the leaderboard. Rank by a different column, see the board before and after.

Train and improve a model

Training holds a GPU and spends credits, so the agent always shows a plan and waits for yes. How it works. Train on what it got wrong. A fine-tune from a benchmark run’s mistakes.
Distill a strong model into a small one. Teach a small model the reasoning a frontier model got right.
Fine-tune on a dataset. A LoRA fine-tune from Hugging Face.
Follow a job. Progress, logs and what happens when it finishes.
Close the loop. Measure the trained model on the same benchmark.

Keep benchmarks in git

Every version of a benchmark in your own GitHub or GitLab repository, committed as BenchGen Agent. The full guide. Connect a repository. The agent asks for a narrow access token and tells you how to make one.
Save a version. After any change you might want to undo.
Review a change first. A pull request you can read and merge.
Go back. Put an earlier version live, after seeing what would change.

Your account

Credits. What you have left and what things cost.
Connect your own agent. Benchmark and trace an agent you built elsewhere.

Tips for better results

“Multiple choice”, “open answers scored on key points”, “a single number” or “tool calls” decides how every answer is marked. If you say nothing, the agent picks, and tells you what it picked.
The agent previews by default, but saying “show me first” or “do not start yet” makes sure a long request stops at the point where you can still change it.
“My latest benchmark”, “the horse care one”, “my last run” and a page link all work. When two benchmarks share a name, the agent tells you how they differ (published or draft, when they were made, how often they were run) and asks which one you mean.
A chat turn has a time limit. Large benchmarks are written in parts: when the agent stops after a batch, reply continue.
The agent answers in the language you write in, previews and findings included.

Explore more

Agent overview

Where the agent lives, what it can see, how it is traced.

Working with the agent

Every task step by step, from a first benchmark to a trained model.

All skills

The capabilities the agent is built from.

What the agent may do

What it changes, what it asks first, what it can never do.
Last modified on October 1, 2026