codexbox: Four Environment Variables and a mkdir Standing Between You and OpenAI’s CLI
I already wrote the “why I ripped the plumbing out of my own repos and built a base image” rant in the aicodebox post, so I’m not doing it again …
aicodebox: One Base Image, Any AI Coding Agent, Four Modes You Didn’t Have To Write
I built claudebox because letting Claude Code run loose on my host was giving me chest pains. It worked. It grew an HTTP API, an OpenAI-compatible endpoint, an MCP server, …
talkies: Tell OpenAI’s Speech API to Go Fuck Itself
I got the OpenAI Whisper API bill for a month of hooking my own tooling up to it and just sat there staring at the number like it had personally …
pibox: Two Env Vars Is All It Took to Wire pi-coding-agent Into aicodebox
I built aicodebox as an abstraction — one base image, an AgentAdapter contract, plug any coding agent’s CLI into it and get the API/MCP/Telegram/cron surface for free. That’s a nice …
telethon-plus: Your Telegram Account as an HTTP API and MCP Server
Telegram has two APIs. The Bot API — neutered, restricted, limited to whatever Telegram decided bots are allowed to do. And MTProto — the actual protocol your phone uses, with …
aigate: Your Own Fucking AI Infrastructure
A 3060 and no cloud budget. AI models behind one endpoint — six cloud providers with free tiers, five local engines that run on your own hardware, the rest on …
claudebox: Claude Code in Docker, Now With Seven Ways to Break Your Production Server
Heads up — this post has been superseded. As of v2.0.0, claudebox is a thin child image of aicodebox — the agent-agnostic base that now owns every surface described below. …