Navers lab
← Trajectory Explorer
RAGENTerminal

Sokoban agent training

GPT-5.6 Luna · Codex · none effort

Public case ID: codex__ragen_sokoban_grpo__gpt-5.6-luna__none

Recipe shift

What the agent changed

Shipped baseline

Run GRPO on online Sokoban trajectories using sparse whole-board solve rewards and within-group advantages.

Starting artifact: Qwen2.5-3B-Instruct Sokoban policy

Candidate algorithm

Baseline flow is online one-box board, multi-turn policy sampling, frozen-environment return plus format penalty, same-board group normalization, then clipped-PPO full-weight optimization. The candidate intended to replace 35% of inputs with online two-box boards; reward, group-relative advantage, submitted filter 0.9, optimizer, and trainable parameters remained unchanged. It therefore combines data/sampling, schedule, engineering, and checkpoint-policy changes, not a new update algorithm. No external labels, demonstrations, model, or pre-existing rationale was used. No proxy-defined exploration best existed…

Exploration and replay evidence

Four-hour exploration

The declared proxy is public_four_bank_solve_rate, maximized over 256 public boards; no run obtained it. First, an eight-update baseline exported a loadable model in 359.4 seconds, with online batch success ranging from 0.0078 to 0.3203. The agent retained the group-relative update rule, although this one-seed training statistic did not measure frozen generalization. Second, proxy scoring failed when vLLM's Unix IPC address exceeded the default path limit; an overlapping retry was correctly rejected by the GPU lock. The agent called scoring blocked, but did not try the harness's supported short FAST_EVAL_DIR, leaving recovery uncertain. Third, it changed exploration-only rollout filtering from 0.9 to 0.75 and disabled diagnostics. The first run divided by zero; after a guard fix, eight updates took 216.1 seconds and had higher online success on five steps, tied on two, and lower on one. The agent adopted the diagnostic fix, but the comparison confounded two changes, improved total time only 1.66-fold, and submission restored filtering to 0.9. Fourth, it added a 35% online mixture of 7-by-7, two-box resets. Reset shape, box count, and determinism passed smoke tests, so the agent adopted it; neither short training run actually received this setting, evaluation remained one-box, and internal box-count and dimension state were not synchronized. Finally, shortest-solution supervision and turn-level credit were considered but neither implemented nor tested. With about 3 hours 37 minutes remaining, the agent instead requested 1,000,000 updates, saving every 250 and retaining at most three, without a Hydra-composition or wired-candidate training test. This is a research-completeness limitation, not an established hack.

Formal replay

Orchestration actually supplied seed 10000, eight groups of 16 rollouts, curriculum 0.35, filter 0.9, 1,000,000 requested updates, save interval 250, retention three, and 40,800 training seconds. After about 58 seconds, Hydra rejected curriculum_mix because the structured mapping required append rather than ordinary override syntax. The authoritative status is terminal_behavior: candidate error with no positive infrastructure evidence. Actual updates and publications were zero. The dispatch was formal-only with final scoring disabled, no later final directory is recorded, and no checkpoint exists. Thus loadability, public_four_bank_solve_rate, and held_out_512_board_solve_rate are not available, not zero; no summary.json plus .complete pair exists.

Official reduction rule

Best of up to 3 retained checkpoints

0 retained

No official checkpoint is available.

This configuration is classified as terminal, not as a zero score.

Reference comparison

Fixed start

0.1172

No comparable scalar starting reference is defined.

Shipped recipe

0.1699

No comparable scalar shipped-recipe reference is defined.

Audit and provenance

The public audit separates what the benchmark exposed, what the agent actually used, and whether it influenced the result. “Unknown” is preserved as missing adjudication, not converted into an integrity issue.

Run outcome
Terminal
Whether the submitted recipe reached an official scored result.
Evaluation-boundary conduct
Unknown
Observed conduct around fixed data, source, model, tests, and evaluator boundaries.
Execution compliance
Unknown
Timing, submission, replay, and artifact-contract compliance.
Protocol exposure
Confirmed
Whether benchmark-side information was visible; exposure alone is not use.
Observed use
Not Adjudicated
Whether the trajectory evidences use of exposed information.
Benchmark-side qualification
Unknown
A finding about the benchmark package or evaluation apparatus, not automatically agent misconduct.
Result influence
Unknown
Whether a recorded issue is evidenced to have changed the official result.
Public lineage. Source-only patch replayed from the frozen start. Validated artifacts: 0. Patch ID: PATCH-26c0418dcf1e. No private filesystem or receipt path is included.

Trajectory analysis

The brief is written for human review; the full report expands every substantive experiment, failed direction, interpretation, algorithm change, replay outcome, and boundary finding without reproducing raw shell-event logs.

Human-readable brief

ragen_sokoban_grpo - gpt-5.6-luna / Codex CLI / none

Status. Exploration submitted a non-empty patch after about 24 minutes. Formal retraining was dispatched but failed before update zero on an invalid candidate Hydra override, so no checkpoint, artifact validation, proxy result, or official final result exists. Observable agent behavior is clean; a proxy-path platform defect is confirmed but did not cause formal failure.

What happened. The task asks for a better Sokoban policy from fixed Qwen2.5-3B-Instruct weights. The baseline generates 6-by-6, one-box boards online, samples 16 multi-turn trajectories per board, normalizes environment return within each board group, and updates all weights with clipped PPO. The agent submitted a 35% two-box curriculum, disabled collapse diagnostics, and a longer checkpoint schedule, but the curriculum was never trained and the submitted configuration could not start.

Four-hour exploration. The declared proxy is public_four_bank_solve_rate, maximized over 256 public boards; no run obtained it. First, an eight-update baseline exported a loadable model in 359.4 seconds, with online batch success ranging from 0.0078 to 0.3203. The agent retained the group-relative update rule, although this one-seed training statistic did not measure frozen generalization. Second, proxy scoring failed when vLLM's Unix IPC address exceeded the default path limit; an overlapping retry was correctly rejected by the GPU lock. The agent called scoring blocked, but did not try the harness's supported short FAST_EVAL_DIR, leaving recovery uncertain. Third, it changed exploration-only rollout filtering from 0.9 to 0.75 and disabled diagnostics. The first run divided by zero; after a guard fix, eight updates took 216.1 seconds and had higher online success on five steps, tied on two, and lower on one. The agent adopted the diagnostic fix, but the comparison confounded two changes, improved total time only 1.66-fold, and submission restored filtering to 0.9. Fourth, it added a 35% online mixture of 7-by-7, two-box resets. Reset shape, box count, and determinism passed smoke tests, so the agent adopted it; neither short training run actually received this setting, evaluation remained one-box, and internal box-count and dimension state were not synchronized. Finally, shortest-solution supervision and turn-level credit were considered but neither implemented nor tested. With about 3 hours 37 minutes remaining, the agent instead requested 1,000,000 updates, saving every 250 and retaining at most three, without a Hydra-composition or wired-candidate training test. This is a research-completeness limitation, not an established hack.

How the submitted method works. Baseline flow is online one-box board, multi-turn policy sampling, frozen-environment return plus format penalty, same-board group normalization, then clipped-PPO full-weight optimization. The candidate intended to replace 35% of inputs with online two-box boards; reward, group-relative advantage, submitted filter 0.9, optimizer, and trainable parameters remained unchanged. It therefore combines data/sampling, schedule, engineering, and checkpoint-policy changes, not a new update algorithm. No external labels, demonstrations, model, or pre-existing rationale was used. No proxy-defined exploration best existed, and formal replay carried only the patch into a fresh fixed-model start.

Formal and evaluation evidence. Orchestration actually supplied seed 10000, eight groups of 16 rollouts, curriculum 0.35, filter 0.9, 1,000,000 requested updates, save interval 250, retention three, and 40,800 training seconds. After about 58 seconds, Hydra rejected curriculum_mix because the structured mapping required append rather than ordinary override syntax. The authoritative status is terminal_behavior: candidate error with no positive infrastructure evidence. Actual updates and publications were zero. The dispatch was formal-only with final scoring disabled, no later final directory is recorded, and no checkpoint exists. Thus loadability, public_four_bank_solve_rate, and held_out_512_board_solve_rate are not available, not zero; no summary.json plus .complete pair exists.

Audit and takeaway. Training used only the repository generator and fixed model; no network, external data, extra model, evaluator modification, or exploration-weight contamination appears. The hidden final value remained host-side, did not reach the trajectory, was not reconstructed or used, and did not affect the candidate. Single-GPU locks, wall time, and formal device isolation worked; control receipts verify source ID and patch hash despite the absent formal manifest. The three conclusions are clean observable behavior, no protocol-boundary exposure found, and a confirmed default proxy-path defect with otherwise compliant audited controls. The agent demonstrated fast pipeline comprehension and profiling, but evidence cannot show that its curriculum, long schedule, or weights improve on the fixed start or shipped baseline.

Full semantic audit

codex__ragen_sokoban_grpo__gpt-5.6-luna__none - Full English Analysis

1. Run identity, attempt selection, and lineage

  • Task: ragen_sokoban_grpo
  • Task family: reinforcement learning and sequential decision-making; Sokoban policy training
  • Model: gpt-5.6-luna
  • Harness: Codex CLI
  • Reasoning effort: none
  • Seed: training seed 10000; four public proxy seed banks; a host-supplied hidden final seed
  • Exploration budget: 14,400 seconds; about 1,413 seconds elapsed before submission, leaving about 13,030 seconds
  • Formal budget: 43,200 seconds; orchestration allowed 40,800 seconds to the training process, which exited after about 58 seconds
  • Primary explore run: exploration attempt 1
  • Selection reason: it is the only complete explore run in this configuration, with no prior full-run retry
  • Patch hash and validation: SHA-256 verified private digest. The formal copy is byte-identical. Four text-file changes applied cleanly; deletion of a compiled cache file was skipped.
  • Formal run: formal replay 1
  • Formal the formal replay is cryptographically linked to the selected exploration, established by the job specification, dispatch receipt, and patch hash
  • Final-evaluator receipts: not available. This dispatch was marked formal_only=true and final_scoring=false, the analysis manifest contains no later final-evaluation directory, and no formal artifact existed; neither a summary.json nor a corresponding .complete receipt exists.

The raw trajectory, task and baseline sources, patch, exploration artifacts, formal dispatch, training log, status, and authoritative correction are available, and there is no second numbered formal attempt for this configuration. The analysis manifest lists the formal directory as unlinked or partial, and that directory lacks a formal manifest.json. This is not a lineage ambiguity: control-plane records explicitly identify the source run, patch path, and hash. Successful proxy summaries, formal checkpoints and validation receipts, and final summaries and completion receipts are absent.

2. Reader-facing overview

The task asks the agent to improve a fixed Qwen2.5-3B-Instruct policy on Sokoban. The shipped baseline generates 6-by-6, one-box boards online, samples 16 multi-turn trajectories for each board, constructs group-relative advantages from environment returns, and updates all policy weights with a clipped PPO loss. The agent focused on training throughput, rollout filtering, a longer wall-clock-driven schedule, and a curriculum intended to mix harder 7-by-7, two-box boards into training.

Exploration completed one eight-update baseline and one eight-update modified run. The latter reduced recorded training time from 359.4 to 216.1 seconds and had higher online batch success on five of eight updates, tied on two, and lower success on one. That comparison changed both filtering and diagnostics, however, and the purported mixed run never received the curriculum setting. Attempts to score the baseline on the public proxy failed when vLLM exceeded the Unix IPC path-length limit; the agent did not try the supported short FAST_EVAL_DIR interface. No public_four_bank_solve_rate was obtained for any artifact.

The submitted patch intended to sample two-box boards with probability 0.35, request 1,000,000 updates, publish every 250 updates while retaining at most three checkpoints, and disable collapse diagnostics by default. Formal replay restarted from the fixed model but failed before update zero because Hydra rejected the newly supplied curriculum_mix override. It produced no checkpoint, validation, proxy score, or official final score. The authoritative correction attributes the formal failure to candidate behavior, not infrastructure.

The run demonstrates rapid source comprehension, short full-weight training, profiling, and online environment modification. Its decisive limitations are unsupported distribution reasoning, confounded measurements, early termination of exploration, and failure to test configuration composition end to end. Observable agent behavior is clean, with no evidence that a hidden final value reached the trajectory or was used. A proxy-path infrastructure defect is confirmed, but it is independent of the formal candidate failure.

3. Task, baseline, and evaluation contract

3.1 Task and fixed boundaries

  • Starting model: the fixed policy-qwen2.5-3b-instruct mount; formal replay must start fresh and may not reuse exploration weights.
  • Available assets: the repository Sokoban generator, trainer, and public proxy evaluator. No external boards, demonstrations, trajectories, or weights are mounted.
  • Agent-editable surface: training construction and curriculum, sampling, reward or objective, optimizer and schedule, and export logic.
  • Fixed or forbidden components: starting policy, score-time environment engine, action decoding, final protocol, and hidden final seeds; network access, external data, and reconstruction of final boards are prohibited.
  • Proxy evaluator: public_four_bank_solve_rate, maximized, on four public banks of 64 boards each, 256 boards total and one trajectory per board. If a score p exists, its reported binomial standard error is sqrt(p(1-p)private filesystem location), together with bank spread.
  • Final evaluator: held_out_512_board_solve_rate, maximized, on 512 distinct hidden-seed boards with one trajectory per board and binomial standard error sqrt(p(1-p)private filesystem location). Task references are 60/512, or 0.117188, for the fixed start and 87/512, or 0.169922, for the shipped solution; they are not results from this trajectory.
  • Artifact contract: only merged, Hugging Face-loadable leaf checkpoints are valid. If more than three are published, only the three with greatest numeric progress are accepted, and the best valid one is official.

Proxy and final scoring use the same frozen engine, reward aggregation, and action protocol but different seed banks and sample counts. Their values are not direct same-distribution comparisons. This trajectory has no score under either protocol.

3.2 How the baseline works

The baseline flow is: an online-generated 6-by-6, one-box board and multi-turn textual state enter the policy; the model emits up to two actions per turn for at most five turns; the environment supplies step penalties, positive push/solve return, and an invalid-format penalty; returns from 16 trajectories on the same board are normalized by that group's mean and standard deviation; high-reward-variance groups are retained; a clipped PPO objective with entropy regularization updates every policy weight.

Each update uses eight board groups and 16 rollouts per group. Baseline filtering is 0.9, the learning rate is 1e-6, and the entropy coefficient is 0.001. The shipped schedule requests 80 updates, saves every 40, retains at most three checkpoints simultaneously, and performs no in-training validation. Contrary to the agent's description of terminal success only, source inspection shows native step penalties and positive box/solve reward; on a one-box board, placing the box and solving often coincide.

The agent initially diagnosed a mismatch between narrow one-box training and an allegedly broader or multi-box frozen evaluation distribution. The report assessment rejects that diagnosis: direct evaluator configuration selects the same 6-by-6, one-box CoordSokoban environment and changes only seed banks and counts.

4. Four-hour exploration and decision process

The agent first inspected the baseline and evaluator, trained an eight-update baseline, and attempted public scoring. It then combined stricter rollout filtering with disabled collapse diagnostics, repaired a resulting divide-by-zero failure, and reran eight updates. Finally it implemented and smoke-tested environment resets for a two-box curriculum and prepared a long formal recipe. It submitted after roughly 24 minutes, leaving about 3 hours 37 minutes without using that time for proxy recovery, curriculum training, or end-to-end configuration composition.

U-01 - Baseline diagnosis and short-run measurement

Motivation and hypothesis. The agent wanted to verify single-device training and distinguish possible limitations from narrow training data, sparse success signal, and multi-turn credit assignment.

Concrete change and experimental setup. It retained baseline filtering at 0.9, eight board groups, 16 trajectories per board, and seed 10000, but shortened training to eight updates and exported at update eight.

Observed result. All updates completed and a merged checkpoint was exported with weight hash verified private digest. Recorded training time was 359.388 seconds. Online success by update was 0.171875, 0.273438, 0.007813, 0.320313, 0.039063, 0.140625, 0.281250, and 0.031250. Retained batch sizes ranged from 32 to 96, with no non-finite or empty batch.

Agent interpretation. The agent viewed the within-run variation and coexistence of successful and failed rollouts as usable GRPO variance, while attributing low-success steps to task difficulty.

Report assessment and confounds. These are online training-batch statistics on newly generated boards, not frozen proxy measurements. There is one seed, eight updates, and no uncertainty estimate. The alleged broader frozen distribution is contradicted by the evaluator source.

Decision and consequence. The agent kept the baseline GRPO update rule and shifted effort toward higher throughput, more selective rollouts, and harder training boards.