Meet the Team - Agent-CloudShell
This was where I started to understand the power the opencode was going to give me. Agent-CloudShell lives in CloudShell! Yay! You can start up CloudShell, install opencode and fire it right up there, so it has unlimited power to really break your AWS deployment. I mean, massive unrestricted access, so writing some clear instructions for it to read in every session is really important. But its context can be magnificent. It has access to the AWS CLI so it can just go and find answers, and it has so much more domain knowledge than I've got in managing AWS.
As a deployment debugging tool its been brilliant, but the problems with trying to copy results from Agent-CloudShell to Agent-Sam was the problem that inspired adding Slack to the agents. Once Agent-Sam (who can see the code but not AWS) was able to directly talk to Agent-CloudShell (who can see AWS and but not the code) then I was able to keep two instances with their separate context windows going and sharing information. This became a trouble-shooting super-powered team.
When I was thinking on how I characterised Agent-CloudShell, then I first thought of Colonel White, sitting in the cloud, and I though of John Tracy monitoring from space, but actually I'm going with Gordon Tracy. Deployed when there is trouble in an inhospitable environment he can go where others cannot.
