Bryan Helmkamp 809b3891b5 Forward every configured sandbox plugin to the Petri worker ... The worker's environment carried only the host, Docker and Daytona plugin variables from the server's own environment, so a run on a third-party provider kind never learned where its plugin was, although the server kept `[server.sandbox.providers.<kind>]` plugin settings for its own attach. The launch spec now derives `PETRI_SANDBOX_<KIND>_PLUGIN` and `PETRI_SANDBOX_<KIND>_SHA256` from every enabled kind's plugin settings, and `PETRI_SANDBOX_PLUGIN_DEV=1` when any of them sets `dev`, set after the allowlist so the settings win over an ambient variable of the same name and the allowlist stays the fallback. The server's default plugin binary name is `sandbox-driver-<kind>`, the name Petri looks up, since one executable serves both sides. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-19 14:45:42 -04:00
..
deploy-railway.mdx	refactor(search): select backend from available credentials	2026-08-21 20:09:52 -04:00
deployment.mdx	feat(deploy): support Tailscale Services deployments (#560)	2026-07-07 22:39:00 -04:00
sandboxing.mdx	Open sandbox provider identity to plugin kinds	2026-09-09 15:17:32 -06:00
security.mdx	refactor(search): select backend from available credentials	2026-08-21 20:09:52 -04:00
self-host-docker.mdx	refactor(search): select backend from available credentials	2026-08-21 20:09:52 -04:00
server-configuration.mdx	Forward every configured sandbox plugin to the Petri worker	2026-09-19 14:45:42 -04:00
troubleshooting.mdx	feat(search): add Venice backend for web_search	2026-08-21 12:31:03 -07:00