gjkim042

> 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.

It was the decision to simplify the architecture. And actually workspace(github) is a persistent layer for kelos.

You can create a new branch and new PR and updage it on next iteration based on comments and existing patch.

That makes a lot of sense.

Thanks for the feedback.

Get 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?

Thanks,

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?

about the adoption friction, You can easily use it by kind create cluster + axon install.

Thanks for your interest. (Sorry for the late interaction, I thought the post was just abondoned.)