Kiro CLI launched ACP support so you can now use agentic capabilities across any client that supports ACP. You can now use Kiro in JetBrains, Eclipse, Zed, or old school Emacs and Neovim. ACP standardizes how code editors and AI agents communicate, allowing any agent and editor

Don't love the memory and context management in Rho. What's cooking should be much better.

Rewrote the entire memory system. Scattered markdown files -> unified brain.jsonl with structured tooling. Git-friendly. Auditable. Also: new review extension, memory viewer v2, web UI performance pass, killed 4 template files that were just clutter. 69 files changed. +11,407

The /review extension might be my favorite new feature. Leave line-level comments. When you submit, the comments get injected back into the conversation as structured markdown so the agent can act on them.

Learning to code was never about learning syntax. It was about: – how systems think – how state changes over time – how abstractions leak – how small decisions compound – how to understand errors and fix When you write code yourself, you are forced to be precise. AI is great

Rho is now installable via pi/npm npm install -g rhobot-dev/rho

/review extension in action

There’s a reason we called the company Entire. We need an entirely new AI-native developer lifecycle. Built from the ground-up for agentic coding.

otlp metrics extension for the pi people: github.com/mikeyobrien/pi…

in the age of clankers, use nix

recommended reading. this feels intuitively right. you can kind of see this in OSS as well, where you'd think the cost to copy is essentially zero now. but it's anything but. OSS that gives into vibeslop or full clanker automation falls apart. OSS that has strong human guidance

I don't know if I'm one of Amazon's "best coders", but I have built a bunch of things over the years. I can say that I'm building more, and manually writing less code, than at nearly any point in my career.

And now it's a Ralph Orchestrator preset github.com/mikeyobrien/ra…

Tried takopi with Rho. Realized it's easier to own the stack for tighter integrations, so now there's telegram support for rho 🤖💬

One of the best parts of open source: someone you’ve never met says your work helped them. Getting those notes about ralph-orchestrator is surreal every time.

Give your agents an email and have them do small tasks like this: "Pick one project and do a fresh-eyes bug sweep. Carefully read new + existing code, find obvious bugs/confusion, fix on a new branch, and email a report. Run only during 08:00-22:00 local time; if outside that

Thank you for the contribution. Rho is now backed by grammy.