Pre-configured Linux container + Stands Agents

[TykoDev]

I begin with saying sorry if you idea is a bit wild but I come for a different "sandbox" than development (old school on-prem+cloud+infrastructure).

What about having a Linux container that had strands-agents SDK with some tools like "Utilities", "Web & Network", "Code Interpretation", "Shell & System" and "File Operations" enabled by default. Add some standard model providers and option to change between bedrock or local storage, wire all the configs into environmental variables to customize at build.

My vision is to have an isolated Linux container (wsl) with a strands-agent + tools enabled and integrated to the OS with essentially full control. How well would it work? How much could the agent "grow" with use of memory etc. could it become increasingly better? how complex tasks could you get it to do?

What do you think, am I crazy or could this work?

[yonib05]

Not crazy at all, @TykoDev, and thanks for sharing it. Sorry for how late this answer is arriving.

Most of the building blocks you describe now exist, and some landed after you posted. The SDK has first-class sandbox support: pass a DockerSandbox to an agent and it automatically gets sandbox_shell and sandbox_file_editor tools whose commands and file operations run inside an isolated container rather than on the host. Docs: sandbox. The design is the inverse of your sketch in one interesting way: the agent process (model calls, state, hooks) stays in your trusted environment and only execution goes into the container, which is a safer default than giving the agent full OS control.

For the tool menu you listed, the sandbox tools above cover shell and file operations out of the box, and anything else on your list is straightforward to add as a custom tool. There's also a Docker deployment guide for packaging the whole agent as a container. Wiring model provider choice and settings through environment variables at build time is plain container practice, nothing in the SDK fights it.

On "growing with use": session management persists conversation state across restarts, and the memory stores let an agent accumulate and retrieve knowledge over time. It won't self-improve unboundedly, but an agent that remembers your environment and past fixes does get noticeably more useful.

[TykoDev]

Since then I have found the hill I will die on. Deno 2 + Strands TS :D, sandbox, FFI, bounch of built in native functions like fetch, and now also native deno compile... Oh, and if you happen to be a windows user like me, then you can throw out docker :D wslc is here!

[yonib05]

Separately, on the "pre-configured" part: an official prebuilt image with all of this set up doesn't exist, and I checked, nothing tracks that yet. If you'd find it valuable, please open a feature request so we can see how much demand there is.