i believe agent native sites will stand up and the incumbents will be forced to adapt
such as agent native shopping platforms whereby a human will bring you something from walmart or what not could spring up and disrupt your instacart of the world
this of course is just one simple example, when it works better for the clawdbot or whatever comes next what are the users going to choose they'll say 'get me some apples from walmart using instacartforbots' because they know the agent success rate will be higher
Frontend QA is the final frontier, good luck, you are over the target.
The amount of manual QA I am currently subjected to is simultaneously infuriating and hilarious. The foundation models are up to the task but we need new abstractions and layers to correctly fix it. This will all go the way of the dodo in 12 months but it'll be useful in the meantime.
agent-browser helped a lot over playwright but doesn't completely close the gap.
i see what you are saying now, i have actually started doing my own dockerfiles so everything is in one container it works reasonably well actually eg you install postgres redis x y and z on the same thing the agent is running on then you can start fresh anytime then all of your stuff is on localhost
Indeed I believe this is probably the next thing to solve but even here I don't think it is out of reach. What we aught to be able to do is disconnect and make asynchronous the goals of the project with where we are. This, in normal software building, is encapsulated by the roadmap. I am building roadmapping prompts now and broadening the scope of the software development lifecycle even further to the encapsulate the roadmap as well which was previously out of scope for the experiment I am running now.
The prompts I am using now give the agent autonomy over 'make the next prd that makes sense' however I think it is a straightforward extension to add 'in the context of the @roadmap/ ' or similar with probably decent results.
Have you tried something similar?
Even without a roadmap the agent continues to do useful work over 24 hours in. You can see the commits and PRDs they really are quite sensible and I pulled and tested and everything really is working quite well. Frankly, I am shocked it is working at all. I have had to step in once or twice you definitely need to keep an eye on the logs every once in a while. Getting the loop booted up in a reliable way was the hardest part to be honest and even that was not terribly difficult.
> the LLMs aren't as good at making 3D objects as they are are writing code
I am still hoping that openSCAD or something similar can grab hold of the community. openSCAD needs some kind of npm as well as imports for mcmaster-carr etc but I think it could work.
Once you get your setup bulletproof such that you can have multiple agents running at the same time that can run unit tests and close their own loops things get even faster. However you accomplish that. Not as easy as it sounds mostly (and absurdly) due to port collision. E2E testing with playwright is another leap.
This deeply resonates. I got out of the game. The issue is that financial freedom was never a technology problem. Meatspace will always get their hands on anything with a moderate amount of traction.
https://github.com/waynenilsen/crumbler
This uses recursive task decomposition but is single thread by design. Honestly fast enough for me and makes it easier to reason about