Skip to content

Conversation

@aluzzardi
Copy link
Member

Just a POC to play around "user defined environments".

The idea is:

  • Every cu installation gets a default environment (stateful)
  • Agents work on that environment, proposing changes, with the user reviewing/merging
  • New sessions automatically resume work in said environment
  • In a multi agent scenario, or experimentation scenario, the user could create a different environment and lead the agent there
# this should happen behind the scenes
$ cu create default

$ goose run --debug -s -t "create a hello world application using flask and a stunning blue design" 
─── environment_list | container-use ──────────────────────────
─── environment_open | container-use ──────────────────────────
environment_id: default
...

$  goose run --debug -s -t "start the hello world app" 
─── environment_list | container-use ──────────────────────────
I see there's a default environment available. Let me open it and check what's inside.
─── environment_open | container-use ──────────────────────────
environment_id: default
Let me check the contents of the environment to find the hello world application.
─── environment_file_list | container-use ──────────────────────────
Now I'll start the application using Python. Since this is a web application that needs to run continuously, I'll run it in the background:
─── environment_run_cmd | container-use ──────────────────────────
background: true

Signed-off-by: Andrea Luzzardi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant