Repository navigation
Restore recorded configuration when resuming runs - #184
Merged
Merged
Conversation
Qian-Cheng-nju
marked this pull request as ready for review
October 9, 2026 06:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resuming a PFS run currently applies fresh CLI defaults unless every original flag is repeated.
run --resume --output-dir DIRnow restores omitted settings from the existing schema-5 execution policy and selects the exact recorded task cohort. Explicit conflicting flags fail before setup, including flags that equal the normal CLI defaults. The source, corpus, toolchain, checkpoint, and session identity checks remain mandatory.Claude Code credential discovery now accepts an explicit OAuth token through the same path as an API key. When cached credentials require a host CLI probe, only that subprocess receives low effort; the experiment's recorded effort and the parent environment stay intact. Normal container preflight still validates the selected model and credentials.
Recovery covers only recorded inputs. Jobs, quota thresholds, and container retention remain operational options; Proof Completion records can restore mode/cohort but do not contain an execution policy. Older PFS manifest schemas fail explicitly and require their original checkout.