They're not really new, we just never really got to them - we just assumed they were there as a force of nature. Let's list them out (I'm sure there are more than this list): * Deployment: Infrastructure is the new bottleneck after coding. * You write
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&
No more MSI. No more dragging. No more downloading. 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
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
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, * how many things a person needs to change to add, change or remove a feature, * how many times
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. https://github.com/inceptionstack/opstalk Quick Install npm
I've spent probably hundreds of $ on loki-agent's code. And spending more every day. It's code that combines: * My expertise and architectural vision and creative ideas * My token budget When I open source it, and you fork it, you're basically building on
It's hard to believe OpenClaw (read "ClawdBot") was released only about 4.5 months ago. Nov 24 Openclaw was released on Github publicly. It's been making history ever since. I'll treat it only from a tech standpoint, but it is a phenomena.
Happy to release bedrockify: An OpenAI Completions compatible API with embeddings proxy API for bedrock usage. Many of the current agents don't support bedorck by default, but do support custom OpenAI api. This gives a proxy you can run easily in one line on the same machine as
This Entry is an Experiment in creating a definition of what stateful agents are along side Opus 4.6. It's based on a technique I read about in Andrej Karpathy's Post: - Drafted a blog post - Used an LLM to meticulously improve the argument over 4 hours.
Now It Codes, Deploys and Debugs Full Stack Apps. It's the full loop. I'm doing it through a deployment harness I created that I call Loki. You can find it here: https://github.com/inceptionstack/loki-agent I think this is a new pattern. maybe a
PSA: embedrock has been superseded by bedrockify which contains both the embedding and the completions inference proxy embedrock is a tiny Go proxy I created (ok, my agent did) that translates OpenAI's /v1/embeddings API to Amazon Bedrock, so your existing AI tools work with Titan and Cohere