Guides migration of historical SWE-Marathon agent configurations to the shared Codex runtime. It preserves native tasks, verification rules, and scoring while outlining environment checks and restrictions on retired execution methods.
Migrate historical SWE-Marathon agent configurations to the shared Codex runtime.
Review the instructions the agent will receive before you install.
Read ../../runtime/RUNTIME.md and ../../../runtime/RUNTIME.md before preparing
a new study. Use the shared Harbor adapter and its explicit execution_mode and
iteration_context, preserving native tasks, verifier policy and scoring.
The historical five-arm WEN framework is retired. Do not run its assisted unblock or sandbox-replacement wrappers, reinterpret withdrawn results, or invent an independent validator from git status. Existing study data and withdrawal notices remain tied to their original source revision.
Validate the chosen native environment with a bounded task before a full run. Model jobs, verifier access and publication require the caller's authorization; loading this migration guide grants none of those actions.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Guide role-specific work in LoopX auto-research, from defining research conditions and proposing hypotheses to experiments, evaluation, and adoption or retirement decisions. Keep evidence, failed attempts, task handoffs, and stopping conditions tied to each worker’s assigned role.
Guides LoopX benchmark experiments through benchmark-toolkit, covering run management, comparisons under matched conditions, and analysis of agent action histories. It helps explain outcomes and efficiency while tracking source versions, score validity, and evidence boundaries.
Review the exact final set of changes for a LoopX goal, checking reuse, simplification, concrete risks, and project validations. Record and verify a quality receipt, a review record tied to those specific changes.
Register lasting project documents in a connected LoopX project's document registry, using metadata that conceals private details. This helps future agents locate relevant designs, research notes, procedures, and other project materials.
Reviews authorized LoopX goals, tasks, and deliveries to explain project progress and identify decisions the owner needs to make. It also guides handoffs to suitable agents while preserving the original objective, constraints, and evidence.
Manage a project's stored materials through inventory, migration, archiving, and ranking based on verified source reads. Changes follow owner approval, preserve material references, and include validation records and rollback procedures.