Recommended integration pattern for remote HTTP sandboxes like Daytona in MAF?

[gimmickj]

Hi team,

We are building a lightweight .NET 10 agent CLI on top of Microsoft Agent Framework.

We are experimenting with integrating a remote HTTP-based sandbox service (similar to Daytona), and we want to avoid going too far in a direction that does not match the intended MAF design.

Our current MVP approach is:

• a session-level sandbox manager
• an AIContextProvider that injects an execute_code tool
• chat/CLI commands for sandbox create/current/exec/upload/download
• session-level sandbox reuse between the agent and the CLI

This works for now, but we are unsure whether this is the recommended long-term pattern.

Our main questions are:

1. For remote HTTP sandboxes, is AIContextProvider + execute_code the recommended integration pattern today?
2. Is Microsoft.Agents.AI.Tools.Shell mainly intended for local / docker / near-host shell execution rather than remote sandbox services?
3. Beyond Hyperlight, is there a plan for a more general sandbox / CodeAct provider abstraction for remote services?
4. If the community wants to build a Daytona-style integration, what is the recommended minimum scope?

We would appreciate guidance before we invest further in the abstraction.

Thanks!