Skip to content

Consume resolved sandbox tool policy#527

Merged
chubes4 merged 2 commits into
mainfrom
fix/issue-523-generic-sandbox-policy
Jun 3, 2026
Merged

Consume resolved sandbox tool policy#527
chubes4 merged 2 commits into
mainfrom
fix/issue-523-generic-sandbox-policy

Conversation

@chubes4
Copy link
Copy Markdown
Collaborator

@chubes4 chubes4 commented Jun 3, 2026

Summary

  • Replace WP Codebox's generated Data Machine sandbox ability list with a generic wp-codebox/sandbox-tool-policy/v1 snapshot contract.
  • Require requested allowed_tools to validate against the caller-provided resolved snapshot before host or browser sandbox launch, failing closed with structured diagnostics when missing or denied.
  • Pass sandbox-visible runtime tool IDs into the sandbox agent contract without interpreting Data Machine-specific taxonomy.

Tests

  • npm run build
  • npm run sandbox-tool-policy-smoke
  • npm run agent-sandbox-code-smoke
  • npm run task-input-contract-smoke
  • npm run wordpress-plugin-smoke

Verification limitation

  • npm run artifact-contract-smoke timed out after 5 minutes twice in the local worktree without producing a failure message.

Closes #523

AI assistance

  • AI assistance: Yes
  • Tool(s): OpenCode (GPT-5.5)
  • Used for: Implemented the generic sandbox policy snapshot plumbing/enforcement, updated smoke coverage/docs, and ran local verification for Chris to review.

@chubes4 chubes4 force-pushed the fix/issue-523-generic-sandbox-policy branch from 9643c65 to c422fa9 Compare June 3, 2026 12:10
@chubes4 chubes4 merged commit 729ceac into main Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consume resolved sandbox tool policy instead of hardcoded Data Machine ability lists

1 participant