Kelos runs Claude Code and Codex in K8s pods that retry when CI fails
At a glance
Kelos orchestrates Claude Code, Codex, Gemini, or OpenCode in ephemeral Kubernetes pods as CRDs—watching bug issues, drafting fix PRs, self-reviewing, and retrying when CI fails—while the author still does final review and merge. This workflow is listed under Claude-Code, Codex, CI, Kubernetes, Agent-Tooling.
CircleCI's Chunk sidecars run scoped microbuilds in Firecracker/E2B microVMs that mirror CI, hooking agent stop/eval events so Claude Code, Codex, or Cursor changes are validated before commit—~27s microbuilds and 3–5× lower token burn on retries in their tests.
Room Service 3.3’s local MCP gives coding agents disk/port/Git visibility and actions like stop-port or trash build data—off by default, local socket only, permanent actions need in-app approval, every action logged.
Product Hunt hit Rill is an AI-native browser where ⌘E turns the current page into a task for Claude Code/Codex—agents work while you keep browsing, with tabs themed and projects centralized.
An HN commenter described a Claude Code setup with reusable skills for a UI library/Storybooks/APIs, a post-change review agent, PR checklist reviews, scheduled docs/coverage agents, and ticket triage that leaves a halfway-done plan on each issue.