I think a running agent periodically checks if a process it started has finished.

I think this is what I’ve been waiting for! Live interactions with models are fundamentally asynchronous! This will be great for interactivity.

What a good time for harness design. Just while OpenCode is growing up a bit and focusing on their harness. I’m delighted to see people focusing on good general solid harness design principles.

Someone make an OpenCode API (the best general agent end UI API I know) compatible server for it!

Sucks that I haven’t upgraded my client to V2 yet and I don’t really want to build on an outdated API ...

Edit: It would be cool to get streaming responses :) But I understand (and actually applaud) that the authors seem to have been very focused on the core mechanics.

Also note that this works with the responses API!

To reduce the codex polling I slapped this into my ~/.codex/config.toml:

  [features.multi_agent_v2]
  enabled = true
  wait_agent_enabled = true
  min_wait_timeout_ms = 10000 # 10s
  default_wait_timeout_ms = 300000 # 5m
  max_wait_timeout_ms = 3600000 # 1h

Seems to do the job and reduce usage; I just ran Astra for ~5 hours (using a goal) and it used the last 30% of my usage. And now they released GPT-6 Sol and Luna (which is basically 5.6 Sol and Luna, but a bit better and also 50% cheaper) ;_;

Do you have any examples of this approach?

"But I don't think you can trademark a generic word like Unreal..."

Sure you can, trademarks are contextual. If they were a landscaping business it wouldn't matter. But within the same industry absolutely.

Those do all seem directly tied to what Unreal Engine does i.e. graphics

Apple? https://en.wikipedia.org/wiki/Apple_Corps_v_Apple_Computer

Unreal is trademarked. This is not in question. And personally I 100% thought this was an agent specifically for dealing with the Unreal Engine, and was interpreting all of that information in that context. Very weird name for a company/product.

Why don't you explain what's different?

I was imagining a talking head avatar rendered in Unreal Engine, with lip sync and facial expressions driven by a multimodal LLM that produces the speech.

omp.sh does this way better by just allowing structural toolcall execution in eval with python/js.

Happy with swival.dev ...

I think the biggest selling point of a codex sub vs a claude sub is that you can use codex subs in any harness you want.

Epic harness -- unreal agent!

I think this space is very untapped. Models are interesting, but I am absolutely obsessed with some things I've been researching/working on for the past few years:

Fractal tool discovery: tool taxonomy where an agent can "drill deeper" to find what specific tool it's looking for. Helps if/when polluting context with a zillion (mostly unnecessary) tools.

Leveraging splay trees: this is my favorite data structure and I think relatively unused in the context of agents/harnesses. A lot of times, recently-used workflows/tool-chains will be used again, so having those at the top of the search hierarchy is an awesome optimization.

Virtual containerized notebooks: models working in sandboxed (WASI) Python notebooks is incredible. Even local models (if given enough time) will usually converge on a good solution. Being able to mount tools/resources/fs is again, imo quite untapped. Some problems here are running native things (thing numpy/pandas) in containers is a nightmare (or impossible).

Anyway, happy to see other folks seriously doing stuff in this space. If anyone wants to collaborate on anything don't hesitate to reach out :) I'm also actively looking for a job or some contract gigs.

Fun times ahead.

happy to see more harnesses in the Go space, i've had a fun time building https://github.com/ChaseRensberger/wingman

i think the language primitives map well to the natural desire to use these tools across networks and in concurrent workloads.

another Go harness i keep up to date with is: https://github.com/boldsoftware/shelley (exe.dev team)

This is not an Unreal Engine agents? Very disappointed