Comment by danudey

9 hours ago

Not sure if this is deliberate or not but you're describing Docker Sandbox extremely closely. https://www.docker.com/products/docker-sandboxes/

1 comment

danudey

Reply
dbmikus  8 hours ago

Yeah, Docker Sandbox is in the right direction. But there's a lot of parts that are still not ironed out yet.

How do you package a Docker Sandbox up into an app that can expose UI widgets, with an agent hiding behind them? What widgets is the agent allowed to modify? How do you run a workflow like "give agent all these files, modify the files, and do changeset management on the modifications?"

I'm not 100% sure which part of these will be baked into the application standard format, and which are orthogonal. But current way of packaging up and running these agents doesn't feel right.

I think about this a lot because my startup is building cloud VMs for agents to do code-gen and auto-validate changes, so we have a workflow like:

    1. git repo, skills, CLI tools, biz context goes in
    2. agent iterates against running dev environment
    3. changes go out into git PRs and CI

I think this type of app/agent workflow will expand outside coding use-cases.