Repository navigation
A13N Harness × FrontierHarness Eval: 21/30 tasks with Kimi K3 #1064
Wh1isper
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We evaluated A13N Harness with Kimi K3 on all 30 FrontierHarness Eval tasks, using the FrontierHarness Eval task set and evaluation methodology. A13N Harness passed 21/30 tasks (70.0%), with $2.93 standardized cost per pass and a 7m 03s median successful-trial time.
The comparison places this local run alongside the 12 published baseline configurations from a frozen upstream snapshot. A13N Harness has the highest observed pass rate in that table; the comparison is provisional because the runtime and provider conditions differ and no matched control was run.
Configuration
c7e287142188dd581ef37daea8fdcfa59f310857bailian-kimi-k3{})frontier-harness-eval/eval@e837a70Instructions
We used our general-purpose Harness UI instructions, without benchmark-specific instruction tuning to reduce token usage or inference cost. The adapter supplied the same fixed task-execution guidance across tasks, alongside the normal Harness UI system prompt. Each benchmark's task instruction was submitted as the user task.
The frozen adapter guidance was:
This guidance sets execution and evaluation-integrity boundaries; it contains no token-saving directives or task-specific solution hints.
Evaluation process and comparability
The evaluation reused the frozen upstream task instructions, task definitions, task payloads, and verifiers. Harbor/Pier prepared the task containers, installed the frozen Harness bundle, ran the real Harness UI App, and collected task-verifier outcomes. Native file, shell, and image-reading capabilities handled the tasks; the adapter did not replace the agent loop. Task-declared tools were connected where required.
The local setup differs from the published Runta baseline: it uses OrbStack with amd64 emulation, different runner versions, an internal model gateway, and local container provisioning rather than Runta golden-snapshot restores. Task network controls remained in place. The clean Meriyah rerun used an offline Python/dependency cache, model-gateway-only agent egress, and a separate offline verifier. Other tasks used their retained task/suite policies rather than this stricter rerun policy.
The upstream reproduction workflow calls for a matched control to establish comparability. We did not run one. Accordingly, the table below is a provisional comparison with frozen published results, not an official upstream leaderboard rank. Pass-rate, cost, cache, and speed differences combine harness behavior with these execution differences.
Full results
Rank is by observed pass rate; ties share a rank. All rows cover the same 30 task identities. Baseline values come from the frozen upstream
results/eval-data.json, not new control runs.Cost coverage is the share of tasks with cost data under each row's reporting scope, rounded to a whole percent. Several baseline cost totals have partial coverage; those costs reflect the available portion. A13N Harness's 100% reported-cost coverage uses the request-exclusion policy below; raw usage is complete for 22/30 tasks. Cache coverage is 100% of successful tasks for every row.
The README chart plots pass rate against cost per pass, with a logarithmic cost axis. The orange star marks A13N Harness; the orange line connects the published baselines' cost/pass-rate frontier only.
Cost, cache, and timing definitions
Costs use the frozen upstream
kimi-k3-2026-08-20pricing table: $3.00 per million fresh-input or cache-write tokens, $0.30 per million cache-read tokens, and $15.00 per million output tokens. These are standardized inference estimates, not a supplier invoice; machine costs are excluded.Input tokens include cached reads and writes. The calculation charges fresh input after subtracting cache reads and writes, then adds the appropriate cache and output charges. First-cold normalization reprices cached reads in each task's first included root generation at the fresh-input rate. For OpenSSL, the initial request had no response or usage, so normalization starts at the first included generation.
Only canonical valid PASS and FAIL results contribute to these totals. Earlier smoke tests, infrastructure-invalid attempts, quarantined attempts, and superseded retries are excluded. Nine failed requests with no response and unavailable usage are excluded from the reported fee scope; their records remain in the raw audit. Their provider charges are unknown, rather than assumed to be zero.
Cost per pass divides the first-cold total across all selected tasks, including failures, by the number of passes. It is different from the median task cost. The table's cache metric is the median normalized cache-read/input ratio among successful tasks, rather than a token-weighted aggregate. Timing uses full-trial wall time, including setup and verification; the cumulative figure sums selected trial durations and is not calendar elapsed time.
Result selection and integrity
for-ofwithusingandofas the binding name. No further quality retry was selected.Per-task results
The first nine rows are DeepSWE tasks; the remaining 21 are Terminal-Bench tasks. Costs below use the first-cold normalization and reported request scope described above. Times are full-trial seconds. Values are rounded for display; aggregate calculations use unrounded data.
A13N Harness solved
datacurve/scc-bounded-memory-spillingin 3,065 seconds. None of the 12 published baseline configurations passed that task in the frozen results.Reproducibility references
The upstream repository owns the task set, evaluation workflow, and published baseline data. This report's tables publish our selected outcomes and aggregate accounting; raw local execution artifacts are retained privately and are not a public reproduction package.
e837a70bd6beb4e72eeeda62dd06e3bd34f6cb63ffd18213a165e985fd7d876395a3f53e00961253a89bbc88420a41374bc20c4cc7e287142188dd581ef37daea8fdcfa59f3108575c095156374024ecf88d321aaccb2264d4e7b083bf80e28ab0a6c555205663ecbada542cbafef661b8f253fb97d58b054131c3b1a327aca2a3f36b7c6367bb46Conclusion
On this 30-task run, A13N Harness passed 21 tasks at $2.93 standardized cost per pass, with a 7m 03s median successful-trial time. The frozen Codex baseline passed 20 tasks at $3.47 per pass and 6m 43s. A matched-control evaluation is the next step for attributing these observed differences to the harness itself.
All reactions