Start with a workflow
Talk to Hue
Talk to Hue
Talk to Hue
By submitting you agree to our Terms & Conditions and Privacy Policy
01
FAQ
Quick Answers
Answers to the questions agent builders ask before they trust a rerun.
01
What does Hue actually preserve from a run?
01
Everything the agent saw and everything it touched: the prompts and context in order, every tool call and its exact response, and the outcome. Enough to rerun the scenario with a different agent and get a fair comparison.
Everything the agent saw and everything it touched: the prompts and context in order, every tool call and its exact response, and the outcome. Enough to rerun the scenario with a different agent and get a fair comparison.
02
My tooling already runs evals on production data. What's different?
02
Those tools re-score a run: they grade what already happened. Hue re-executes it. The agent runs again inside the same conditions, so you learn how a new model or prompt would have behaved, not how the old run would grade.
Those tools re-score a run: they grade what already happened. Hue re-executes it. The agent runs again inside the same conditions, so you learn how a new model or prompt would have behaved, not how the old run would grade.
03
Does an agent need to be deployed first?
03
Yes. Hue works from real runs, so it needs production or staging traffic.
Yes. Hue works from real runs, so it needs production or staging traffic.
04
How are third-party tools simulated?
04
Every tool call in the original run is served back with the same response and behavior, so reruns never hit a live service and never drift from the original scenario.
Every tool call in the original run is served back with the same response and behavior, so reruns never hit a live service and never drift from the original scenario.
05
What can I compare?
05
Any version of your harness — prompts, tools, orchestration — and any model, against the same preserved run. Accuracy, cost, latency, side by side.
Any version of your harness — prompts, tools, orchestration — and any model, against the same preserved run. Accuracy, cost, latency, side by side.
01
FAQ
Quick Answers
Answers to the questions agent builders ask before they trust a rerun.
01
What does Hue actually preserve from a run?
01
Everything the agent saw and everything it touched: the prompts and context in order, every tool call and its exact response, and the outcome. Enough to rerun the scenario with a different agent and get a fair comparison.
Everything the agent saw and everything it touched: the prompts and context in order, every tool call and its exact response, and the outcome. Enough to rerun the scenario with a different agent and get a fair comparison.
02
My tooling already runs evals on production data. What's different?
02
Those tools re-score a run: they grade what already happened. Hue re-executes it. The agent runs again inside the same conditions, so you learn how a new model or prompt would have behaved, not how the old run would grade.
Those tools re-score a run: they grade what already happened. Hue re-executes it. The agent runs again inside the same conditions, so you learn how a new model or prompt would have behaved, not how the old run would grade.
03
Does an agent need to be deployed first?
03
Yes. Hue works from real runs, so it needs production or staging traffic.
Yes. Hue works from real runs, so it needs production or staging traffic.
04
How are third-party tools simulated?
04
Every tool call in the original run is served back with the same response and behavior, so reruns never hit a live service and never drift from the original scenario.
Every tool call in the original run is served back with the same response and behavior, so reruns never hit a live service and never drift from the original scenario.
05
What can I compare?
05
Any version of your harness — prompts, tools, orchestration — and any model, against the same preserved run. Accuracy, cost, latency, side by side.
Any version of your harness — prompts, tools, orchestration — and any model, against the same preserved run. Accuracy, cost, latency, side by side.
01
FAQ
Quick Answers
Answers to the questions agent builders ask before they trust a rerun.
01
What does Hue actually preserve from a run?
01
Everything the agent saw and everything it touched: the prompts and context in order, every tool call and its exact response, and the outcome. Enough to rerun the scenario with a different agent and get a fair comparison.
Everything the agent saw and everything it touched: the prompts and context in order, every tool call and its exact response, and the outcome. Enough to rerun the scenario with a different agent and get a fair comparison.
02
My tooling already runs evals on production data. What's different?
02
Those tools re-score a run: they grade what already happened. Hue re-executes it. The agent runs again inside the same conditions, so you learn how a new model or prompt would have behaved, not how the old run would grade.
Those tools re-score a run: they grade what already happened. Hue re-executes it. The agent runs again inside the same conditions, so you learn how a new model or prompt would have behaved, not how the old run would grade.
03
Does an agent need to be deployed first?
03
Yes. Hue works from real runs, so it needs production or staging traffic.
Yes. Hue works from real runs, so it needs production or staging traffic.
04
How are third-party tools simulated?
04
Every tool call in the original run is served back with the same response and behavior, so reruns never hit a live service and never drift from the original scenario.
Every tool call in the original run is served back with the same response and behavior, so reruns never hit a live service and never drift from the original scenario.
05
What can I compare?
05
Any version of your harness — prompts, tools, orchestration — and any model, against the same preserved run. Accuracy, cost, latency, side by side.
Any version of your harness — prompts, tools, orchestration — and any model, against the same preserved run. Accuracy, cost, latency, side by side.