Interesting seeing other people's approaches to orchestration.<p>I've been working on Pullboard and just open sourced it: <a href="https://github.com/pullboard-dev/pullboard" rel="nofollow">https://github.com/pullboard-dev/pullboard</a><p>To me, orchestration is not really the core problem. The bigger challenge is handling agent coherency over long periods of time, (drift) so my solution is a living forum-like system where agents shout to one another, document work in items, and follow doctrine handed down by the developer and work against a known specification that's checkable. I have used this workflow in several large projects that MUST be correct, and it works for me. Currently cleaning it up for other users.
Not saying this counts specifically but I love seeing devs who hate Jira build something like Jira to solve managing a team of agents. It’s a beautifully ironic thing to watch.
I think we'll see it more and more... open-ended Q&A / novel work is everyone's first experience of LLMs, but I don't think it's actually representative of most of the work people do. Coding kind of sits in the middle as it's novel but semi-structured.<p>Chat is great for novel open-ended work, but is terrible at concurrency - i.e. managing > 1 agent runs. As agents get cheaper, I suspect we'll see more more bounded processes where you want to run lots of items through them at once, and thus Jira-like things... (we ended up having this problem and building something like this, albeit more medieval themed [0])<p>We also found the other piece that Jira-style solves (and that chat makes super hard) is multi-player. I've yet to see a good implementation of a multi-player chat solution to agents working concurrently; and we found that an async model is the only sane solution to this.<p>[0] <a href="https://pumpup.com" rel="nofollow">https://pumpup.com</a>
Gas Town did the same thing back in January. It's probably got three more layers of abstraction on top of it by now.<p><a href="https://yegge.ai/gastown" rel="nofollow">https://yegge.ai/gastown</a>
I don't think people hate issue tracking system, they just hate Jira.
And I think most people who hate Jira actually just hate the process their company has imposed inside of Jira.<p>The vanilla out of the box product is actually quite close to old Trello, in simplicity. But there are so many ways to fuck it up and overcomplicate it, and so many companies proceed to fuck it up and overcomplicate it.
+1<p>I have learned recently that I don't inherently hate JIRA, I hate <i>our</i> JIRA and byzantine process flows.<p>I think because other task trackers like Trello are simpler and have less config options (per my last use, long ago, pre-Atlassian-acquisition), it's impossible <i>knock on wood</i> to get into the antipatterns I've seen in those tools.<p>Ironically I think one of the main goals of management I have seen consistently over time - ensuring tickets are accurate, up to date, and reflect reality - would end up much more true if the task tracking tools were just much simpler, with fewer fancy features.
This is absolutely it for me. I've never had to use a Jira instance that wasn't absolutely ruined by its maintainers.
I actually just hate Jira :) It's horrendously slow for what it does, the search is mediocre at best, and I regularly run into bugs.
Yup, I literally just hate their web UI. Once I found the Atlassian-blessed jira "cli" [0] (after searching for a long time for a tui, which is actually what the "cli" is primarily) I have actually be fine with using Jira again. As an added bonus, being a cli has made it easy to interface with using my AI tooling.<p>[0] <a href="https://github.com/ankitpokhrel/jira-cli" rel="nofollow">https://github.com/ankitpokhrel/jira-cli</a>
Exactly. A plain basic issue tracking system is all that's needed for 90% of cases.<p>Need a specific feature? Plug that in later when you actually need it.
> The local-first work board for teams of coding agents. Nothing ships until a second agent verifies it.<p>> gate: failing<p>Gave me a good chuckle. Cool idea though, and I like the records. Reminds me a bit of the OpenAI hacking incidents.
Haha. Locally it was passing. That badge is GitHub running the tests on its own machines, where a couple of new browser tests fail. Fix is going through the same loop: one agent fixes, another verifies, then it merges.
> docker-agent lets you create and run intelligent AI agents that collaborate to solve complex problems — no code required.<p>How is "no code required" a selling point when we all have agents that can almost instantly puke out all the mostly-correct code you could want?
Code means a bit of mental engagement, more than yaml, json etc. You either review that or not review that, but it's an addition. While I am not touching anything made by docker-the-bloater anytime soon, I could think that at least.
While I love new open source dev (especially in Go!), agent harnesses are turning into JS frameworks from yesteryear.<p>All the cool kids have one!
With the advent of LLMs my one true hope for humanity was the final death of the "JS/ilk things" like Electron, React Native, other things like that, and the culture of "everything is TS/JS or can be turned into that". Looks like it's rather growing exponentially.
Coupled with VSCode forks to manage them
You know which one will win for sure. ones with the worst experience.<p>Vue and svelte are easy to use and learn/adopt. But look what won. React.js.<p>So whatever the ai agent with the vast user basae will win regardless.<p>---<p>I know it's a slippery slope, but given you brought up JS framwork analogy, I had to fall into it
It's all about what story you can tell.<p>Cursor is easily the worst experience I've had with an AI harness, yet it was acquired for billions of dollars in spite of being a middleman tied to a ripoff of VS Code. None of the colleagues of mine who were touting it last year are still using it. But if you can make yourself look like <i>the next big thing</i>, you'll get money thrown at you. Just look at Omarchy.<p>A good experience necessarily takes time and careful thought. Nobody these days can do that while also remaining relevant, or even surviving.
Many people genuinely prefer React over Vue/Svelte
A good model with svelte make things buttery smooth.
I mean as someone who was there at the time, early React was easy to learn and adopt. It’s complexity came later after it had already won<p>Now Angular v1, man… if I ever see another digest loop error in my life, I will scream
So glad I never had to deal with Angular, especially v1. I tried learning it and it just seemed like it would actually make applications more incomprehensible than before. React originally addressed the actual problem that most frameworks mistook for not being that important. I still don't particularly like React, but it makes sense why it became popular.
"Look, LLMs will free you from the tyranny of frameworks!"<p>"Uh, OK, so how do I get this thing working? Where are the docs?"<p>"Well, first you install its unique framework..."
[flagged]
[flagged]
Go doesn't have a good mod/plugin story for harness devs to provide to their users<p>I say this as a gopher who also has a custom harness written in Go, it's a real challenge compared to the TS setups, but TS plugins are also a security concern
Somehow Mattermost, written in Go, allows plugins.
I agree! Comes with the territory of a compiled language I suppose?<p>I haven't given this much thought (I also just started with golang last year) but I'm assuming the only real path here is to provide extension SDKs in Lua or other languages whose interpreters have been implemented in go.<p>I think that's what grafana's k6 [1] does with a JS interpreter<p>[1] <a href="https://github.com/grafana/k6" rel="nofollow">https://github.com/grafana/k6</a>
I was thinking I recalled something like that, but the nice thing about the TS ecosystem is that you can write the same language, importing and using the harness sdk types.<p>Go has the plugin package, but I haven't actually seen anyone use it (outside of toys and blog posts)<p><a href="https://oneuptime.com/blog/post/2026-01-25-plugin-system-go-plugin-package/view" rel="nofollow">https://oneuptime.com/blog/post/2026-01-25-plugin-system-go-...</a>
curious your thoughts on my approach: <a href="https://docs.wingman.actor/extend/plugin-quickstart/" rel="nofollow">https://docs.wingman.actor/extend/plugin-quickstart/</a>
Why isn’t IPC good enough?
My custom harness has a dagger based environment, binary runs in the host, every tool call and file modification creates a new layer in a container - for better session time travel and forking<p>It may work for some things, but you really want to be wired into that system to do the more interesting things.
none are as great as <a href="https://wingman.actor" rel="nofollow">https://wingman.actor</a>!<p>jk its trash
<a href="https://docker.github.io/docker-agent/configuration/sandbox/" rel="nofollow">https://docker.github.io/docker-agent/configuration/sandbox/</a><p>If, like me, you couldn't find any security-related info on the linked page.
Docker Agent is a harness. There is a sandbox mode that can be used to run it in docker sandbox (a VM, not a container). If you don't use sandbox mode then I assume it is running in a container.<p>If you don't want to use their harness then you wouldn't use docker agent and instead use their `sbx` cli to run the harness of your choice (claude, codex, pi, etc).<p>I think it will be great if Docker can get people used to using secure VMs. I am developing a similar project (still a work in progress): <a href="https://github.com/gregwebs/agent-vm" rel="nofollow">https://github.com/gregwebs/agent-vm</a>
i remember going through the entire docs of docker sandbox and there was not one mention of attack vectors. did they fix that?
I'm honestly getting lost between what primary usecase/workflow each of these is intended for:
1. <a href="https://kagent.dev/" rel="nofollow">https://kagent.dev/</a>
2. <a href="https://github.com/kubernetes-sigs/agent-sandbox" rel="nofollow">https://github.com/kubernetes-sigs/agent-sandbox</a>
3. <a href="https://github.com/docker/docker-agent" rel="nofollow">https://github.com/docker/docker-agent</a> (this project)
4. <a href="https://docs.langchain.com/oss/python/deepagents/sandboxes#sandboxes" rel="nofollow">https://docs.langchain.com/oss/python/deepagents/sandboxes#s...</a>
5. <a href="https://www.cloudflare.com/products/sandboxes/" rel="nofollow">https://www.cloudflare.com/products/sandboxes/</a>
Last year (2025), I lost count of how many times I tried using an LLM to set up Docker. It was still the era of prompting, then copy-pasting the response and seeing if it worked... and it almost never did. It’s great to see this new Docker agent. For me, it would be even more appealing to see an agent and a model specialized in Docker working together, capable of proposing advanced configurations and getting them working on the first try.
Modern models should be better with mainstream technologies like docker engine or docker compose, but still to try to help them we started to work on distributing skills ( <a href="https://github.com/docker/skills" rel="nofollow">https://github.com/docker/skills</a> ) in addition of our specialized agent (gordon) integrated in various products.
I tried really hard to make this work for me a couple of weeks ago but it was the brittlest harness out of any that I've used. I'd come back when it's more mature.
Docker Agent <i>could</i> be beneficial for research studies. For example, while writing a ML paper about agents I need to rerun experiments so that:
- others can repeat my results
- validate that variability from LLMs is not causing overconfidence in the results<p>But currently uv is good enough to create isolated, repeatable environments. And it isn't limited to Linux like standard Docker. So when I want to test small samples on my local PC's GPU (Windows or mac) before running on beefier hardware, I can do that easily.
I mean, if you're going to do that at scale, not that you are, but something like <a href="https://github.com/kvcache-ai/AgentENV" rel="nofollow">https://github.com/kvcache-ai/AgentENV</a> is much more suitable for research purposes
personal plug :) <a href="https://github.com/oguzbilgic/kern-ai" rel="nofollow">https://github.com/oguzbilgic/kern-ai</a>
The models are converging (directionally), and the rest of us, including all these agent harnesses, are trying to figure out how to stay relevant
they hope they can annoy and email every person in the org asking for money , same way as they did it with docker.<p>looks like a weird abstractions. why do i need this if i have modal.com, e2b, cloudflare that use original docker + some toolings around + way to run + isolations on network level.
I'm curious about these agent harness frameworks that release their harness before they've released a good agent on top. It's a little cart before the horse.
What does this have to do with Docker?
I guess people at Docker wanted to make an agent.<p>Having it docker branded, I could understand. It’s confusing but the docker brand is strong.<p>But exposing it as a docker subcommand is very confusing to me.
You don't really have to use the docker agent sub-command. docker-agent is a standalone binary. When it was created, though, 1.5 year ago, the idea was that it would be the docker compose for agents (original name was cagent, compose for agents).<p>But it evolved differently and although it runs very well in docker containers and docker sandboxes, it also runs very well anywhere else.
It reads to me like chasing trends
That's the economy we've always been in. X is popular, if your company doesn't have a solution for X you're irrelevant.
that's all docker has been doing for years.
the tools and features certainly indicate so
Based on the repo short description and the first sentence of the readme:<p>It is called 'Docker' as the company, and it has nothing to do with the container technology.
The quest for staying relevant.
This made me laugh. Not sure why. But the whole situation is very absurd now.
It's the Docker you know and love... with AI!
Docker is rapidly fading into irrelevance now that they have missed their strategic acquisition interval via the Microsoft collab misstep, and now has to hype chase as fewer and fewer people believe in their long term viability as a company.<p>Great tech. Not a business.
>What it is, what it isn’t<p>Yep, open ai sol model wrote that.
It frustrates me that there's a prisoners dilemma in communicating this to other humans. If I flag it and write it out (as you've done) I've let the author know that they're losing trust and let others know that they should be more skeptical. I've also created the perfect eval data pair for the ai labs. It's deeply frustrating.
I think the cat is out of the bag.<p>There was a brief point in time at the beginning of the internet where if you saw an image online you could be kind of confident that it hadn't been manipulated significantly... But somewhere around the mid to late 2000s it became prudent to just assume any image you've seen online got at least a blemish filter pass through something like Photoshop.<p>Same thing now with written text. Sometimes you'll be a little bit more or less sure than an llm produced the output but never able to say 100% confidently.
AI is going to eradicate, for good, all trust in the Internet.<p>That's a benified "not a drawback".
Your probably spare yourself some RSI by inverting this and only writing out a message when you find human generated content on hn
Bringing first-class agent orchestration directly into containerized environments is a logical step for secure, reproducible developer workflows.
Pretty vague
If Docker is containerized resources ( cpu, memory, iops, network) with configured limits , I would like to see more ACLs around command and credential restrictions<p>Something like a containerized sudo ACL for commands and for network credential , scoped by oauth scope<p>That way you could truly establish boundaries for an agent before it’s launched , and it could request additional permissions during execution .
Why can't we set the harness? Seems like the missing piece
very weird. why does this have dockers name on it? might as well use an agent harness from kohl's or steak n' shake. odd..
It was created to be the docker compose for agents. 2 years ago, people, including ourselves, started to mix agentic loops and non agentic components in docker compose files. We created docker agent to make this more powerful.<p>At the end, the link with docker compose is just the yaml form. Which by the way can be replaced with hcl files or Go code.
What's new or interesting here? Docker's AI story ought to be around sandboxing, yet the word appears nowhere. Oh, and it's YAML, which I despise.
gimmick
is there a word for enshittification by ai?
i mean... what's the point.<p>just use and customise Pi.<p>Nothing else even comes close.
[flagged]
[flagged]
[flagged]
[dead]
Just what I need in my life; more YAML! /s<p>I'm not sure why anyone would want this. Is there something this actually does better than any other harness? Do current harnesses suck that bad at orchestrating things like Docker? If I do all my work inside a Linux VM and tell an agent inside of it what I need done, it figures out everything, including container orchestration.<p>The very job that AI gents are meant to do should mean that most of the documentation for this Docker Agent is obsolete/unnecessary.
> Go<p>Nowadays there are only two justifiable public languages you should be using for anything
a) C++
b) Rust<p>Rust itself is dubious due to abysmal compile times and the fact that the only guarantees it gives you are of security (aka a skill issue). Modern LLMs write C++ that is as safe if not safer than Rust. Any other language choice is objectively wrong.<p>* For those inquisitive enough the keyword "public" is doing all the heavy lifting here. Pretty much everyone should be developing and using an in-house DSL at this point.
Yeah well I'm doing everything in AssemblyScript.
This is an almost rage bait take, but in any case I agree that the models ability to write correct code and fuzz and test that code does make language choice a different tradeoff than it was before.