Would you welcome a plimsoll sandbox example in the code-sandbox docs?

[carrollco]

Would you welcome a contributed plimsoll example alongside the existing code execution sandbox recipe?

I maintain plimsoll, an Apache-2.0 code execution sandbox, currently pre-1.0. It gives Trigger.dev agents a separate sandbox for running generated Python and JavaScript, including an option to operate the sandbox on your own infrastructure.

The existing integration follows your documented lifecycle:

• Warm the sandbox in onTurnStart.
• Reuse it for executeCode calls, keeping variables and files between calls on session-capable backends.
• Close it in onChatSuspend or onComplete.

There is already a deployable Trigger.dev starter, including a verification task that checks state persists between two Python calls without calling an AI model. There is also a Docker Compose recipe for self-hosted workers, tested on one host with Trigger.dev v4.7.2.

I’d propose a short optional example showing the tool setup, lifecycle hooks, and deployment requirements. It would explain the isolation choices and limits, including requiring gVisor for the self-hosted production example and the daemon’s access to the Docker socket.

Would a small documentation pull request be useful, or would you prefer a link to the maintained starter?

[matt-aitken]

We will release our own sandbox product pretty soon but we're happy to share content you separately create about things like this

[carrollco]

Thanks, Matt. I'm already using Trigger.dev to orchestrate jobs, with plimsoll handling sandboxed code execution. I posted the self-hosted walkthrough here: #5006. Would that be useful content for you to share? Also, will customers be able to run your upcoming sandbox on their own infrastructure, or will it be hosted only?