How to use Claude to build operator workspace features
Claude workers implemented coo-cli workspace and handoff features from an AARE plan, with COOMerger handling merges inside an actively developed Kubernetes operator.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Implement [workspace and handoff features] in [repository] from [approved plan]. Partition tasks by domain and layer to avoid shared-file edits, and provide workspace context from [live project state].
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- bobbydeveaux
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reports that workspace and handoff features were planned by AARE, coded by Claude workers and merged by COOMerger. The overall project was still early and actively being built.
- Human involvement
- The author describes engineering the operator and addressing merge conflicts, but does not describe manual review of these feature changes.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Have the AARE agent plan the workspace and handoff features.
- Run Claude workers inside the operator to implement those features.
- Merge the resulting work through the COOMerger controller.
The author reports using itsacoo, a Kubernetes operator for coordinating coding agents, to develop parts of its own tooling. The concrete example concerns workspace and handoff features in coo-cli. Itsacoo's AARE agent planned those features, Claude workers running inside the operator coded them, and the COOMerger controller merged the work.
The broader development system accepts a plain-English concept and produces planning documents and a task breakdown before assigning work. Concurrent editing created a substantial obstacle: the author reports frequent merge conflicts with naive approaches. Their response was a horizontal slicer that partitions work by domain and layer. It models potential shared-file edits upfront and restructures the task graph to avoid collisions. The author says conflicts became the exception rather than the common case.
The handoff feature fetches live Kubernetes resource state, renders a CLAUDE.md containing project context, and injects it into a pod. The project remained early and actively under development when posted. Who it's for: developers coordinating multiple coding agents who already work with Kubernetes and need explicit task ownership and workspace handoffs.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · bobbydeveaux
Frequently asked questions
Which parts did Claude actually build?
The author identifies the coo-cli workspace and handoff features: AARE planned them, Claude workers coded them, and COOMerger merged them.
How did the author reduce merge conflicts?
A horizontal slicer partitions work by domain and layer, models agents touching the same file, and restructures the task graph to avoid those collisions.
More details
About this account
Planning, implementation and merging were assigned to separate agents and controllers inside the operator.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=47333635. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: bobbydeveaux on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
itsacoo · coo-cli · Kubernetes · COOMerger
Kubernetes · Multi-agent development · Workspace handoffs
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.