AI-assisted development journal
Pull requests deliver implementation when what you need is intent. Someone forks your repo and hands you code, but code is the easy part in an agentic workflow. An agent can generate it from a clear specification. What you actually need is the idea behind the contribution, what the software should do that it doesn’t yet. A PR obscures that under code you didn’t need in the first place.
We’re ripping GitHub out of the Ralph pipeline tonight. PRs, webhooks, status polling, automerge, all of it goes. GitHub becomes a place we push to for safekeeping and nothing more.
Rel-12 is light on features but useful from a development perspective. With headless mode and framebuffer reads, Claude can now launch Ikigai, interact with it, and see what’s on screen. That changes how we build. This week was model coverage, provider bug fixes, and early e2e testing, laying groundwork so the next few releases can move faster.
I’ve never looked at Ikigai’s source code. Not once. Fifteen weeks into a project with 1,100 files, 173,000 lines of C, and a custom terminal renderer, and I couldn’t tell you what most of the functions are named. That’s not neglect. It’s the experiment.
Yesterday we wrote about building for the machine, the idea that if an LLM is building your software, your software needs interfaces the LLM can use. Today we shipped the implementation: a Unix domain socket that lets Claude drive Ikigai like a human sitting at the keyboard.
Agents can finally manage themselves. Rel-11 gives agents the tools to fork children, send messages, wait for results, and clean up after themselves without a human touching a single slash command.
Ikigai is a black box. It renders to the alternate terminal buffer, reads keystrokes one byte at a time, and produces nothing an external tool can see or touch. That’s fine when a human is sitting at the keyboard. It’s a dead end when the thing building the software is an LLM that can’t see your screen.
When we started Ikigai twelve weeks ago, we chose C. The reasoning was straightforward: if you want a tool to land in Linux distributions, C is the path of least resistance. Package maintainers understand it, build systems support it natively, and there’s no runtime to drag along. We were building software meant to be installed through apt and dnf, sitting alongside the rest of the system tools. That assumption turned out to be rooted in a world that’s already disappearing.
Two days ago we published “See Ralph Run,” a post about our nano-service orchestration layer. It’s already stale. Not because anything broke, but because the thinking underneath it shifted. That’s life in agentic development right now: write something on Monday, rethink it by Wednesday, rebuild it by Friday.
We finally spent ten minutes on production value. The Ikigai Devlog YouTube channel now has actual thumbnails instead of random freeze frames, courtesy of Google’s image generation throwing robot illustrations at us until something stuck.