feat: isolate sandbox session outputs and enforce tenant writes - #961
Open
yaojin3616 wants to merge 16 commits into
Open
feat: isolate sandbox session outputs and enforce tenant writes#961yaojin3616 wants to merge 16 commits into
yaojin3616 wants to merge 16 commits into
Conversation
Y1fe1Zh0u
added a commit
that referenced
this pull request
Aug 14, 2026
The v1.11.4 Runtime resolves dynamic MCP tools through durable execution bindings, while the sandbox PR test still mocked the retired name-only helper. Point the test at the binding resolver without weakening either contract.\n\nConstraint: Preserve v1.11.4 Tool execution binding semantics while integrating PR #961.\nRejected: Restore the name-only MCP helper | duplicates routing state and weakens execution integrity.\nConfidence: high\nScope-risk: narrow\nDirective: Sandbox tests must mock the same binding boundary used by Runtime execution.\nTested: 59 scoped sandbox, Tool validation, and builtin contract tests passed.\nNot-tested: Full backend suite at commit time.
Y1fe1Zh0u
added a commit
that referenced
this pull request
Aug 14, 2026
PR #961 adds one execute_code policy lookup and publication metadata to every sandbox dispatch. Update existing mocks and catalog assertions to model those now-required inputs while preserving the no-reexecution outcome contract.\n\nConstraint: Integrate isolated Session output without weakening existing AgentBay readiness or unknown-execution safety.\nRejected: Hide the execute_code policy lookup in production | would make model guidance diverge from the active sandbox policy.\nConfidence: high\nScope-risk: narrow\nDirective: Sandbox backend mocks must expose the active workspace and publication contract.\nTested: Three previously failing integration tests passed.\nNot-tested: Full backend suite at commit time.
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.
Summary
/opt/clawith/venvtenant_idfor tenant-scoped DAO writes, migrate Runtime chat-message writers, and add a safe NULL tenant backfill scriptdb=None, and fix the LLM model tenant UUID double-conversionValidation
uv run pytest -q tests/test_sandbox_execution_policy.py tests/test_sandbox_subprocess_backend.py tests/test_agent_tools_storage_workspace.py tests/test_base_dao.py tests/test_agent_runtime_a2a_completion.py tests/test_agent_runtime_trigger_completion.py tests/test_llm_model_tenant_scope.py tests/test_api_database_dependencies.py— 57 passedgit diff --cached --check— passed./scripts/arch-guard.sh— passed (legacy warnings only)163:3009environment; backend healthydelivered