3 ms·
Show HN: Kelos – Define your AI coding agent workflow as YAML on Kubernetes
Kelos is a Kubernetes framework for orchestrating autonomous AI coding agents (like Claude Code) in ephemeral pods.
The original goal was sandboxing — I didn't want to run agents with --dangerously-skip-permissions locally. But the real unlock turned out to be declarative workflows. You define agent tasks as Kubernetes CRDs, things like:
- Watch for "bug" issues → auto-draft a fix PR
- Auto-review incoming pull requests
- Auto-triage new issues with labels and priority
- Periodically scan the codebase → propose improvements
- Test the project as a new user → surface rough edges
Self-development pipeline: https://github.com/kelos-dev/kelos/tree/main/self-development https://github.com/kelos-dev/kelos/tree/main/self-developmen...
I've been using Kelos to develop Kelos. When something breaks, I refine the YAML or add features to the controller. It's early and rough around the edges, but the core loop works.
Happy to answer questions about the design or what's broken.
- jlongo78 7mo ago[flagged]
- gjkim042 7mo agoThanks, Actually, Kelos captures structured outputs after each coding task compeletes: the final branch, the created PR link if exists, input/output tokens, and so on. And coding agent’s logs would remain after finished as a container log. Is theere anything you want to add additionally?
- jlongo78 7mo ago[flagged]
- gjkim042 7mo agoGet the idea. I was wondering what’s the real scenario that needs agent chaining? I implemented the task chaining using “dependsOn” field, but there’s no real usage now. Can we just write a pipeline prompt using the numbering? 1. Do this, 2. And do this?… When do you think it’s useful to chain coding agents step by step?
- mrgaro 7mo agoI'm an avid user of the Claude Code planning feature and I like how Claude Code asks for questions. I also often iterate the plan before finally giving it a go. How do you solve this in Kelos? I tried to check the code base, but it didn't really provide any glues. I guess I could instruct the agent to build a plan and to post the plan in the issue and then iterate that with written comments in the issue. Is that how you run it?
- gjkim042 7mo ago> I guess I could instruct the agent to build a plan and to post the plan in the issue and then iterate that with written comments in the issue. Is that how you run it? Exactly. I simply just create an issue if there's a simple bug and let Kelos handle it. If there's a complex issue that I'd like to build a plan for before implementing it, I build the plan locally and let the agent create a github issue for it, then Kelos will handle it.