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
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
I asked OpenClaw with opus 4.6 to deep dive into its source code and create a detailed architecture document. I like the output for this and I think others could find use for it since I didn't see it described in this detail so far.
As an architect, I love doing diagrams. I think visually. In the past I loved using Miro, mermaid, and a bunch of others, but only recently (past week!) did I try and experiment with drawIO and its XM files format. This whole post is just about a fun late night
What better time is there to try out a new tool or service than when joining a new company? Well, I just recently joined AWS as a Sr. Solutions Architect. Yay! And that's my opportunity to try out a bunch of stuff that I get a chance to
A common thing for me and other developers I see do (I was first alerted to this by Harel Coman) . We work mainly with cursor but a few use claude code. But a common pattern is this: Start chat, then: 1. Enter Prompt 2. Choose model for this prompt 3.
A while ago I wrote about Zero-Touch Algorithm Handoffs: How We Ship ML Algorithms to Prod Without Rewrites (or ML Engineers) and a few weeks ago I got the chance to speak about this topic at the BuildStuff conference. Here's the video: Summary In this video I break
In a previous blog post I wrote about RepoSwarm: Give AI Agents Context Across All Your Repos . A few weeks ago I spoke at BuildStuff conference about this tool including a deep dive into its architecture and what you can do with it. Here's the link to the
My colleague, Harel Coman, wrote about a new AI-driven code review pattern he's been implementing lately called Red Queen Code Review. I like this idea. If I had to put it in a sentence: Every Code Review "issue" must change either your code, or the AI