[flagged]
Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR
71–77 of 77 posts
Re: Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR
#72The parallel execution model makes sense for independent tickets but I'm wondering what happens when agent A is halfway through a PR touching shared/utils.py and agent B gets assigned a ticket that needs the same file. Does the orchestrator do any upfront dependency analysis to detect that, or do you just let them both run and deal with the conflict at merge time?
[flagged]
Re: Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR
#73Earlier quoted context omitted.
There are a few things: a) you can create CI/build checks that run in github and the agents will make sure pass before it merges anything b) you can configure a review agent with any prompt you'd like to make sure any specific rules you have are followed c) you can disable all the auto-merge settings and review all the agent code yourself if you'd like.
> to make sure you've really got to be careful with absolute language like this in reference to LLMs. A review agent provides no guarantees whatsoever, just shifts the distribution of acceptable responses, hopefully in a direction the user prefers.
Yep, I was gastowning some draft PRs to get a prototype built quickly. The polecat FE PR managed to request a review from @claude (normal ok), and then given that in isolation the PR was fine due to having hardcoded draft schemas (though it was deliberately only ever going to work against a PR deployed version of the API that was also draft), decided to enable auto-merge, such that the PR actually merged and luckily I caught the CI/CD run and locked deployments, however, it would have taken down the site and pointed it to staging.
Re: Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR
#74Earlier quoted context omitted.
Oh good question, I haven't thought deeply about this. Right now nothing special happens, so claude/codex can access their normal tools and make web calls. I suppose that also means they could figure out they're running in a k8s pod and do service discovery and start calling things. What kind of features would you be interested in seeing around this? Maybe a toggle to disable internet connections or other connections…
Network policies controlling egress would be one thing. I haven't seen how you make secrets available to the agent, but I would imagine you would need to proxy calls through a mitm proxy to replace tokens with real secrets, or some other way to make sure the agent cannot access the secrets themselves. Specifically for an agent that works with code, I could imagine being able to run docker-in-docker will probably be r…
[dead]
Re: Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR
#75The feedback loop is what most people miss when they build these systems.
You spin up the agent, it submits a PR, CI goes red, and suddenly
you're back to being the bottleneck you were trying to eliminate.
One thing I ran into building something similar, agents are surprisingly good at fixing the exact error message they're given, but terrible at recognizing when they're going in circles. After the third retry on the same failing test, you're not getting a fix, you're getting increasingly creative excuses for why the test is wrong.
How deep does the self-healing go? Is there a retry limit before it escalates, or does it just keep going until you manually intervene?
Re: Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR
#76Earlier quoted context omitted.
I mean, having unit tests and not allowing PRs in unless they all pass is pretty easy (or requiring human review to remove a test!). A software engineer takes a spec which "shifts the distribution of acceptable responses" for their output. If they're 100% accurate ( snort ), how good does an LLM have to be for you to accept its review as reasonable?
We've seen public examples of where LLMs literally disable or remove tests in order to pass. I'm not sure having tests and asking LLMs to not merge things before passing them being "easy" matters much when the failure modes here are so plentiful and broad in nature.
[flagged]
Re: Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR
#77[flagged]