Pattern: Agent-Owned Accounts (Deploy Environments)
Sign in<br>Subscribe
Give an agent a VM, it will submit PRs. Give an agent a deployment environment and an admin ability, and it will code, deploy, debug and monitor your apps.
I believe LowKey was the first I to have its own AWS account to do with as it pleases. Lately I've also heard of Cloudflare Temporary accounts for agents.<br>These ideas solve for the next problem down the chain: After coding friction is solved, deployment & configuration friction becomes the next bottleneck.<br>Just like "Markdown is the new Installer" , solving the friction of deploying something onto a user's machine, so can we, the developers, solve the deployment problem by giving agents an account that they own.<br>In an internal experiment (~100 participants) Agent-owned accounts have been very impactful for internal solutions architects I've worked with over the past few months - it has sped up prototyping (turned prodo-typing) from weeks/days to mere hours of the most complex proofs of concepts and prototypes you can imagine on an AWS infrastructure with amazing scale.<br>We're slowly showing this to customers (it's open source they can try it now) and getting feedback - but it makes a huge difference. Mobile support is a killer feature. 24/7 live event-based notifications, checks and monitoring a killer feature. Being able to think about something and just try it in a few minutes from your phone while on a the train is a killer feature. removing the friction of configuration and "glue" work is a killer feature.
For now I believe it is pretty risky to give an agent full production account deploy abilities (yet), but how about a sandbox account - one where the agent can utilize the ability to deploy and then fully test a full application end to end, replicating production fully, and then tearing it down if needed, or keeping it and providing access to internal or external beta users using a login?<br>This would take days or weeks in many companies today, and breaks the product-market-fit cycle of feedback-change-deploy. Now it can happen in minutes.<br>Today, base44 , lovable and friends provide just the basics of what you could deploy on, for anything else (graph databases, workflows, storage etc) they rely on you connecting to 3rd parties and giving them your APIs.<br>With a full cloud provider such as AWS, Azure, GCP - these abilities become much more powerful - and there is zero friction to deploy almost anything of any complexity or scale (only wallet depth).<br>Graduating to production will be the brainstorm of a future post.
Read more
Markdown is the new Installer
No more MSI. No more dragging. No more downloading.<br>A well crafted bootstrapping prompt provided to your users can mean you can create ever more complex tools and apps that might be terrible to install from a human-perspective, but for an agent they are easy-as-pie to go through.
Your users
Prodo-typing
production-shaped prototype in a separate cloud environment
This is all me just brain-storming with myself, and I'd love to hear what people think about this. For background Loki is a builder agent based on openclaw designed to be deployed in its own AWS cloud account with full ownership
Software Engineering Practices (are also) Useful for Token Reduction
Software engineering practices were (at least when I'm pushing them) all about minimizing things for humans:
* minimize how much a person needs to read to understand the meaning of something,<br>* how many things a person needs to change to add, change or remove a feature,<br>* how many times
opstalk - a cli to talk to AWS DevOps Agent
So, I think Devops Agent is great. I went ahead and built a small CLI to talk to it directly from my terminal. I think it's pretty cool and makes it easy t to jump in and investigate things fast.<br>https://github.com/inceptionstack/opstalk
Quick Install
npm
Powered by Ghost
Robot Paper
A Blog About AI Patterns & Anti Patterns
Subscribe
Email sent