Latest note
Working between standard and custom Codex builds
My current setup uses an Ollama-enabled Codex fork as a specialized worker runtime alongside the OpenAI-signed build.
Read noteProblems, decisions, and discoveries from ongoing systems work, written down when they seem worth remembering.
Latest note
My current setup uses an Ollama-enabled Codex fork as a specialized worker runtime alongside the OpenAI-signed build.
Read noteA curated path through investigations, measured debugging, and recovery work.
Reducing repeated registry work with cached catalog data, paginated tag loading, and event-driven cache warming.
What looked like a context-size or memory problem on my Strix Halo system turned out to be a model-loading problem tied to mmap.
Using a workflow runner to recover access to a host, and why runners need to be treated as serious infrastructure.
Registry operations, delivery, and the project behind them.
Running and evaluating AI systems on local hardware.
Build infrastructure and practical network systems.
Operating services and the systems around them.
Practical safety boundaries for AI-assisted systems.
My next round of Codex work added Ollama model discovery, provider-aware Desktop selection, a cloud-only root picker, and task-shaped worker qualification.
After plaintext transport worked, I added role-aware concurrency, context rollover, worker inspection, cleanup, and safe private tools.
I changed Codex to route multi-agent messages by provider, keeping encrypted transport as the default while adding a plaintext path for Ollama-compatible endpoints.
Set up email for an existing website domain with Cloudflare forwarding, a Gmail mailbox, and Resend SMTP.
Auto review is useful safety infrastructure, but it can quietly become a large part of Codex usage when tasks keep crossing protected boundaries.
How deterministic retrieval, reusable semantic context, and smaller models can reserve frontier-model attention for the work that needs it.
What code graphs can tell an agent, what real repository questions demand, and why useful memory needs a semantic layer.
An introduction to RepoMemory, a local context layer that helps coding agents find the right part of a repository.
Why the goal is mixed-provider Codex delegation, and where today’s provider path breaks down.
Why prompt injection is dangerous, what adversarial testing can catch, and why passing those tests is not a guarantee of safety.
What looked like a context-size or memory problem on my Strix Halo system turned out to be a model-loading problem tied to mmap.
Building a remote MCP server so AI agents can ask for real time, timezone, and duration data instead of guessing.
Using a workflow runner to recover access to a host, and why runners need to be treated as serious infrastructure.
Reducing repeated registry work with cached catalog data, paginated tag loading, and event-driven cache warming.
Registry Control Plane is now public on GitHub, along with its container packages.
A short note on making the registry control plane easier to use on phones and smaller tablets.
Using a temporary local BuildKit cache in a Forgejo runner to speed up repeated registry control plane builds on limited hardware.
A May 2026 snapshot of building a registry management layer around Docker Distribution.
Operational changes that made my OpenWrt ASU builds more reliable when the official builders were overloaded.