[Draft] Vendor-neutral coding harness for CNCF contributors Suggester: Julien Semaan Type: Initiative As CNCF maintainers and contributors gain access to AI-assisted coding tools through OSS and CNCF perks, there’s a growing risk of tool sprawl and vendor lock-in. Vendors don’t always guarantee how long these subscriptions will last, and maintainers who adopt tools like GitHub Copilot, Claude, or Codex as their primary agentic harness can end up tied to a specific ecosystem. The issue isn’t just the model, it’s the workflow. These tools bundle the model, agent logic, and execution patterns together. Switching tools often means reworking how you build, review, and iterate on code. This initiative proposes exploring a vendor-agnostic agentic harness that separates the workflow from the model. The goal is to give maintainers a consistent interface that works across providers, supports existing tools, and stays flexible as new ones emerge. A shared harness would make it easier to switch models without changing how you work, and to mix and match models depending on the task. It also helps reduce fragmentation across projects and makes workflows more sustainable over time. Some options to explore include Opencode, Nanocoder, and Pi, along with identifying gaps where new approaches may be needed. Deliverables - Example repo(s) for each vendor-agnostic option - Blog post on the CNCF blog and other platforms that have reach to CNCF project maintainers - Maintainer track/summit presentation in Kubecon Salt Lake 2026