walgit with a GitHub Enterprise Server facade — git over smart HTTP from an object-store bucket

Whiteboard is an open-source desktop app where humans and agents can architect software together in a common workspace.

A harness wraps a model. A rig wraps your harnesses. Define your agent team in YAML, boot it with one command. Claude Code and Codex in the same rig, managed as one system.

OpenRig turns AI coding agents from a pile of terminal sessions into a persistent, organized team. Talk to a lead agent about the outcome you want; it can coordinate specialists across teams and bring you results and decisions that need your attention. Start with a repository and one useful change, then keep the team's work and context at the same addresses.

As a part of the journey to transition Netflix's compute infrastructure to be more Kubernetes-native, we have leaned into incorporating components from the Kubernetes ecosystem into our container platform Titus. One example of this is our use of Kueue, a cloud-native job queueing system for batch workloads, which has largely replaced the custom queuing and scheduling logic in our homegrown managed batch solution Compute Managed Batch (CMB).

Server-side apply matters because Kubernetes objects are shared state: it moves field ownership into the API server, so apply-style tools can surface conflicts instead of hiding them as silent overwrites.

I maintain an app that builds on top of kubernetes port forwarding, so i track KEP-4006 because the streaming protocol underneath keeps changing. I wrote about this back in april 2024 around Kubernetes 1.30, and six releases later it's changed enough to be worth another look.

You've got ten Claude Code agents running. Each is working on a different issue. Agent 3 just created a PR that conflicts with Agent 7's changes. Agent 5 has been stuck on "Analyzing codebase…" for 45 minutes. Welcome to multi-agent chaos. Turns out, scaling AI coding agents from 1 to 10+ is a completely different problem from running a single agent in a terminal.

Cilium runs in the kernel-level networking path of millions of Kubernetes pods. If our supply chain were compromised, the blast radius would not be small. Hardening the project against that scenario is something we work on continuously, and we wanted to write down what we actually do, in detail. Most of what follows isn't Cilium-specific: any open source project running CI/CD on GitHub Actions can apply these patterns.

A short debugging story about a two-year-old credentials file, an EKS cluster, and the AWS credential chain quietly doing exactly what it was designed to do.

As you'll know if you've ever tried to build a reasonably sized microservices application locally, you can run out of system resources quickly. So, in order to free up some of that valuable memory, I figured I'd offload things to a Kubernetes cluster running on some relatively cheap hardware, and in this post I'll describe the steps I took so that you can do the same.