Skip to main content
Forking creates a child run that inherits the parent’s sandbox and harness. The child starts from the parent’s final workspace state, so any files the parent wrote are available to the fork.
You can also fork later from another script:
Forks reuse the parent’s sandbox and harness. They can’t be changed on the fork call — create a fresh run if you need a different harness or sandbox.