In your use case you wanted to control codex from docker agent thus you used our harness integration ( https://docker.github.io/docker-agent/features/harnesses/ ). It was not codex calling docker agent which should work with ACP ( https://docker.github.io/docker-agent/features/acp/ ). We could effectively look at using ACP from docker-agent to control others harnesses if it's useful.
replyCombination with Codex is indeed not the most common use case around us. I'll see what can be improved. Sorry that it broke your workflow!
replyHow is not using it with the most popular coding agent not a common use case?
replyNot the most common use case around them: likely meaning that the Codex harness isn’t used that often internally at Docker, is what I would surmise, at least that is how I read it.
replyI work at another big tech company, and up until recently that would’ve been true for us as well (but it’s changed now, we partnered with OpenAI)