fix: make default Daytona + Grok/Codex sandbox runs work #1094
Merged
AlemTuzlakmerged 7 commits into
main fromrefs/pull/1094/head·merged by AlemTuzlak View on GitHubShowing 46 changed files with 32 additions and 1 deletion (loading 43).
x
@@ -0,0 +1,12 @@
+---
+'@tanstack/ai-sandbox': patch
+'@tanstack/ai-sandbox-daytona': minor
+'@tanstack/ai-grok-build': patch
+'@tanstack/ai-codex': patch
+'@tanstack/ai-acp': patch
+'@tanstack/ai-claude-code': patch
+---
+
+fix: make default Daytona + Grok/Codex sandbox runs work without extra wrappers
+
+Headless Grok and Codex stay permissive when policy is deny-only plus default allow. Daytona remaps `/workspace`, starts stopped sandboxes on resume, keeps secrets out of create-time envVars and command strings, and uses native fs/git plus session stdin. Nested skills project by name. Durable Grok journals when durability is wired.
@@ -53,7 +53,7 @@
-| `sandboxMode` | Codex sandbox: `'read-only'` (harness default), `'workspace-write'`, or `'danger-full-access'`. This is the safety boundary on a server. |
+| `sandboxMode` | Codex sandbox: `'read-only'`, `'workspace-write'`, or `'danger-full-access'`. Default is `'workspace-write'` on local-process and Docker. Default is `'danger-full-access'` on Daytona and Cloudflare, because those providers cannot create a nested bubblewrap namespace. Isolation is then the outer VM plus `defineSandboxPolicy`. |