Evaluate KODE on SWE, TB2, and Tau through a standalone benchmark adapter layer, without coupling benchmark logic to the SDK repository.
- Runs
swebench-verifiedthrough Harbor - Runs
terminal-bench@2.0through Harbor - Runs official
tau-bench - Uses the published npm package
@shareai-lab/kode-sdk - Pulls benchmark frameworks dynamically at runtime
- Supports GitHub Actions smoke tests and larger benchmark runs
- Produces merged summaries and per-task result artifacts
Install dependencies:
npm installRun local validation:
npm run typecheck
npm run bench:bundle:harbor
npm run bench:bundle:tauModel names use provider/model format.
Example:
glm/glm-5
+----------------------+
| GitHub Actions |
| SWE / TB2 / Tau |
+----------+-----------+
|
+------------+-------------+
| |
v v
+---------------+ +---------------+
| Harbor Path | | Tau Path |
| SWE / TB2 | | Tau |
+-------+-------+ +-------+-------+
| |
v v
+---------------+ +---------------+
| Harbor Adapter| | Tau Adapter |
+-------+-------+ +-------+-------+
| |
v v
+---------------+ +---------------+
| Node Runner | | Step Runner |
+-------+-------+ +-------+-------+
\____________________ ____________/
\/
+----------------------+
| @shareai-lab/kode-sdk|
+----------------------+
Use the manual dispatch workflows:
.github/workflows/eval-swe.yml.github/workflows/eval-tb2.yml.github/workflows/eval-tau.yml
Minimum required input:
model_name=provider/model
Typical repository configuration:
OPENAI_API_KEYOPENAI_BASE_URLOPENAI_APIANTHROPIC_API_KEYGEMINI_API_KEYMINIMAX_API_KEY
For OpenAI-compatible GLM routing, the harness reads:
OPENAI_API_KEYOPENAI_BASE_URL
Common workflow inputs:
model_nametask_namestask_limitshard_countmax_parallel_shardsn_attemptsn_concurrent
model_nametau_envtask_splittask_idsstart_indexend_indexnum_trialsmax_concurrency
Each run produces:
- shard artifacts
- per-task
result.json agent/kode-result.json- merged summary markdown
- merged results JSON
- merged per-test details JSON
Each run produces:
- final metrics JSON
- per-task reward data
- per-task trajectory data
See:
README.zh-CN.md