Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR (opens in new tab)

(github.com)

42 pointsjawiggins13h ago25 comments

I think like many of you, I've been jumping between many claude code/codex sessions at a time, managing multiple lines of work and worktrees in multiple repos. I wanted a way to easily manage multiple lines of work and reduce the amount of input I need to give, allowing the agents to remove me as a bottleneck from as much of the process as I can. So I built an orchestration tool for AI coding agents:

Optio is an open-source orchestration system that turns tickets into merged pull requests using AI coding agents. You point it at your repos, and it handles the full lifecycle:

- Intake — pull tasks from GitHub Issues, Linear, or create them manually

- Execution — spin up isolated K8s pods per repo, run Claude Code or Codex in git worktrees

- PR monitoring — watch CI checks, review status, and merge readiness every 30s

- Self-healing — auto-resume the agent on CI failures, merge conflicts, or reviewer change requests

- Completion — squash-merge the PR and close the linked issue

The key idea is the feedback loop. Optio doesn't just run an agent and walk away — when CI breaks, it feeds the failure back to the agent. When a reviewer requests changes, the comments become the agent's next prompt. It keeps going until the PR merges or you tell it to stop.

Built with Fastify, Next.js, BullMQ, and Drizzle on Postgres. Ships with a Helm chart for production deployment.

25 comments

pianopatrick1h ago

I wonder, based on your experience, how hard would it be to improve your system to have an AI agent review the software and suggest tickets?

Like, can an AI agent use a browser, attempt to use the software, find bugs and create a ticket? Can an AI agent use a browser, try to use the software and suggest new features?

ramon156new4m ago

I think it's more important to pin down where a human must be in order for this not to become a mess. Or have we skipped that step entirely?

smokeyfish31m ago

Datadog have a feature like that.

raised_hand41m ago

Why K6? Is there a way I could run it without

naultic4h ago

I'm working on something a little similar but mines more a dev tool vs process automation but I love where yours is headed. The biggest issue I've run into is handling retries with agents. My current solution is I have them set checkpoints so they can revert easily and when they can't make an edit or they can't get a test passing, they just restart from earlier state. Problem is this uses up lots of tokens on retries how did you handle this issue in your app?

jawigginsOP4h ago

Generally I've found agents are capable of self correcting as long as they can bash up against a guardrail and see the errors. So in optio the agent is resumed and told to fix any CI failures or fix review feedback.

denysvitali5h ago

FWIW, a "cheaper" version of this is triggering Claude via GitHub Actions and `@claude`ing your agents like that. If you run your CI on Kubernets (ARC), it sounds pretty much the same

MrDarcy7h ago

Looks cool, congrats on the launch. Is there any sandbox isolation from the k8s platform layer? Wondering if this is suitable for multiple tenants or customers.

jawigginsOP7h ago

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 outside of the container?

verdverm55m ago

I love k8s, but having it as a requirement for my agent setup is a non-starter. Kubernetes is one method for running, not the center piece.

conception6h ago

What’s the most complicated, finished project you’ve done with this?

jawigginsOP6h ago

Recently I used to to finish up my re-implementation of curl/libcurl in rust (https://news.ycombinator.com/item?id=47490735). At first I started by trying to have a single claude code session run in an iterative loop, but eventually I found it was way to slow.

I started tasking subagents for each remaining chunk of work, and then found I was really just repeating the need for a normal sprint tasking cycle but where subagents completed the tasks with the unit tests as exit criteria. So optio came to my mind, where I asked an agent to run the test suite, see what was failing, and make tickets for each group of remaining failures. Then I use optio to manage instances of agents working on and closing out each ticket.

abybaddi0094h ago

Does this support skills and MCP?

jawigginsOP1h ago

Yup. MCP can be configured on a repo level. At task execution time, enabled MCP servers are written as a .mcp.json file into the agent's worktree. Enabled skills are written as .claude/commands/{name}.md files in the worktree, making them available as slash commands to the agent

antihero7h ago

And what stops it making total garbage that wrecks your codebase?

jawigginsOP7h ago

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.

1 more reply

upupupandaway7h ago

Ticket -> PR -> Deployment -> Incident

hmokiguess6h ago

the misaligned columns in the claude made ASCII diagrams on the README really throw me off, why not fix them?

| | | |

jawigginsOP6h ago

Should be fixed now :)

j / k navigate · click thread line to collapse

Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR (opens in new tab)

(github.com)

42 pointsjawiggins13h ago25 comments

Optio is an open-source orchestration system that turns tickets into merged pull requests using AI coding agents. You point it at your repos, and it handles the full lifecycle:

- Intake — pull tasks from GitHub Issues, Linear, or create them manually

- Execution — spin up isolated K8s pods per repo, run Claude Code or Codex in git worktrees

- PR monitoring — watch CI checks, review status, and merge readiness every 30s

- Self-healing — auto-resume the agent on CI failures, merge conflicts, or reviewer change requests

- Completion — squash-merge the PR and close the linked issue

Built with Fastify, Next.js, BullMQ, and Drizzle on Postgres. Ships with a Helm chart for production deployment.

25 comments

pianopatrick1h ago

I wonder, based on your experience, how hard would it be to improve your system to have an AI agent review the software and suggest tickets?

Like, can an AI agent use a browser, attempt to use the software, find bugs and create a ticket? Can an AI agent use a browser, try to use the software and suggest new features?

ramon156new4m ago

I think it's more important to pin down where a human must be in order for this not to become a mess. Or have we skipped that step entirely?

smokeyfish31m ago

Datadog have a feature like that.

raised_hand41m ago

Why K6? Is there a way I could run it without

naultic4h ago

jawigginsOP4h ago

denysvitali5h ago

FWIW, a "cheaper" version of this is triggering Claude via GitHub Actions and `@claude`ing your agents like that. If you run your CI on Kubernets (ARC), it sounds pretty much the same

MrDarcy7h ago

Looks cool, congrats on the launch. Is there any sandbox isolation from the k8s platform layer? Wondering if this is suitable for multiple tenants or customers.

jawigginsOP7h ago

Oh good question, I haven't thought deeply about this.

What kind of features would you be interested in seeing around this? Maybe a toggle to disable internet connections or other connections outside of the container?

verdverm55m ago

I love k8s, but having it as a requirement for my agent setup is a non-starter. Kubernetes is one method for running, not the center piece.

conception6h ago

What’s the most complicated, finished project you’ve done with this?

jawigginsOP6h ago

abybaddi0094h ago

Does this support skills and MCP?

jawigginsOP1h ago

antihero7h ago

And what stops it making total garbage that wrecks your codebase?

jawigginsOP7h ago

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.

1 more reply

upupupandaway7h ago

Ticket -> PR -> Deployment -> Incident

hmokiguess6h ago

the misaligned columns in the claude made ASCII diagrams on the README really throw me off, why not fix them?

| | | |

jawigginsOP6h ago

Should be fixed now :)

j / k navigate · click thread line to collapse