Repository navigation
Bind the Environment workspace before preparation - #572
Merged
Merged
Conversation
…onment-workspace # Conflicts: # contracts/agents-api/zh/harness-onboarding.md # docs/zh/runtime-protocol.md
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.
Environment preparation and file operations could start before the agent host knew the Environment’s workspace, leaving custom workspaces inconsistent with native execution. Bind the frozen workspace before every operation, retain it across reconnects and epochs, and map public
/workspacefile and setup paths onto that root.Reject workspace collisions with view-owned paths before creating owners or effects. Resolve the initial native working directory atomically beneath the world root, while preserving environment
noneand subsequent process spawning. Update the protocol and English/Chinese documentation together.Validation: fresh independent blind review found no issues after fixes; focused Go/vet, changed concurrency race tests (50 repetitions), privileged view/real Sandbox I/O, four PostgreSQL binding paths, generated SQL/contracts, cross-build and documentation checks passed. Real Codex, Claude and MiniMax custom-workspace qualification passed. The fixture now explicitly tells the model not to overwrite its pre-set randomized variables; assertions are unchanged. Public Core and remote Provider qualification follows on the integrated branch. Focused checks passed again after merging current cutover.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.