AstroAgentBench
Collection
An agent benchmark on space mission design tasks: paper, RL environments, traces and an interactive space • 3 items • Updated
Claude Code traces preview
Mon, May 18
hi 4
messages Sun, May 10
Please solve the prepared Earth-observation scheduling case using the files in `case/`.
Write `solution.json` at the workspace root. You have a 2-hour timeout, so preserve a valid or likely-valid `solution.json` as soon as possible and keep improving it in place. Focus first on a valid observation schedule, then push coverage toward higher-value tasks. 2
messages 91
tools Please solve the prepared Earth-observation scheduling case using the files in `case/`.
Write `solution.json` at the workspace root. You have a 2-hour timeout, so preserve a valid or likely-valid `solution.json` as soon as possible and keep improving it in place. Focus first on a valid observation schedule, then push coverage toward higher-value tasks. 1
message 75
tools Please solve the prepared Earth-observation scheduling case using the files in `case/`.
Write `solution.json` at the workspace root. You have a 2-hour timeout, so preserve a valid or likely-valid `solution.json` as soon as possible and keep improving it in place. Focus first on a valid observation schedule, then push coverage toward higher-value tasks. 1
message 36
tools Please solve the prepared Earth-observation scheduling case using the files in `case/`.
Write `solution.json` at the workspace root. You have a 2-hour timeout, so preserve a valid or likely-valid `solution.json` as soon as possible and keep improving it in place. Focus first on a valid observation schedule, then push coverage toward higher-value tasks. 3
messages 148
toolsSun, May 3
Please solve the prepared deep-space communication scheduling case using the files in `case/`.
Write `solution.json` at the workspace root as a JSON array of scheduled tracks. You have a 2-hour timeout, so preserve a valid or likely-valid `solution.json` as soon as possible and keep improving it in place. Prioritize valid communication time first, then satisfy as many requests as you can. 1
message 84
tools Please solve the prepared deep-space communication scheduling case using the files in `case/`.
Write `solution.json` at the workspace root as a JSON array of scheduled tracks. You have a 2-hour timeout, so preserve a valid or likely-valid `solution.json` as soon as possible and keep improving it in place. Prioritize valid communication time first, then satisfy as many requests as you can. 2
messages 139
tools Please solve the prepared deep-space communication scheduling case using the files in `case/`.
Write `solution.json` at the workspace root as a JSON array of scheduled tracks. You have a 2-hour timeout, so preserve a valid or likely-valid `solution.json` as soon as possible and keep improving it in place. Prioritize valid communication time first, then satisfy as many requests as you can. 3
messages 133
tools Please solve the prepared deep-space communication scheduling case using the files in `case/`.
Write `solution.json` at the workspace root as a JSON array of scheduled tracks. You have a 2-hour timeout, so preserve a valid or likely-valid `solution.json` as soon as possible and keep improving it in place. Prioritize valid communication time first, then satisfy as many requests as you can. 2
messages 116
tools Please solve the prepared deep-space communication scheduling case using the files in `case/`.
Write `solution.json` at the workspace root as a JSON array of scheduled tracks. You have a 2-hour timeout, so preserve a valid or likely-valid `solution.json` as soon as possible and keep improving it in place. Prioritize valid communication time first, then satisfy as many requests as you can. 1
message 73
tools AstroAgentBench Traces
Native sessions from the AstroAgentBench agent run archive, version v1: 73 Codex rollout files and 42 Claude Code session files. Open a session in Hugging Face Data Studio to inspect its timeline, tool calls, and results.
This is the subset supported by HF's native trace viewer, not the complete experimental corpus. OpenCode, Kimi CLI, other session formats, and non-session run artifacts remain in the Zenodo archive. No sessions have been converted. Experiment, run, system, and case directory structure is preserved under sessions/.
The JSONL files are copied byte-for-byte from the frozen redacted archive. Credentials and personal home paths were scrubbed during archive preparation. Publication verifies the pinned archive manifest, every selected file's SHA-256, JSONL structure, and known plaintext credential/home-path patterns. Opaque encrypted reasoning payloads are retained and excluded from plaintext scanning. release-manifest.json records source provenance, selection counts, and the published file checksums; zenodo-23084447.1 identifies this immutable selection.
Attribution
Source: Wang, Weiyi; Chen, Xinchi; Gong, Jingjing; Huang, Xuanjing; and Qiu, Xipeng. AstroAgentBench agent run archive, v1 (2026), DOI 10.5281/zenodo.23084447. Distributed under CC BY 4.0. This distribution selects supported sessions and adds a dataset card and release manifest; the selected session contents are unchanged.
- Downloads last month
- 80