
Problem 01 is live
AI engineering moved to the systems around the model. Same model for everyone. A real environment. A hidden eval. Improve the loop until the number goes up.
How it works
The starter is already in the editor, with traces that fail. You do not burn a run just to watch it lose. Read those, then change the loop.
System prompt, every tool call, every result, the grader verdict. This is how you debug a harness.
Thirty hidden tasks. Same model. Pass is 85 percent. A careful loop lands higher, with tokens still in budget.
The starter is already in the editor. Read a failing trace, then change the loop.
Start problem 01FAQ
The software around the model: the loop, the tools, the context, retries, when to stop. Not the model. That file is what you write here.
If everyone picks a different model, you cannot tell who built the better loop. Same model, same environment, same hidden eval. The only variable is the harness.
The full transcript of one task: system prompt, every message, every tool call and result, the final answer, the grader verdict. You debug from this, not from the score.
Run is three visible tasks so you can see the failures. Submit is thirty hidden tasks. The number that counts is Submit.
85% on the hidden set, inside the step, token, and time budgets.
One Python file. from harness import llm, tools, Task. The starter is a naive ReAct loop.
Run is free without an account. Submit (the hidden set) needs a login — 5 per day.
No. Switching models is not the skill we measure.
A cheap pinned model. Run is three tasks. Submit is five a day.
Temperature 0. Deterministic fixtures. We always show the number.
Tasks fan out. Results stream into the trace as they finish.