> **NOTE**: to read the design doc join the ate-dev mailinglist in the repo README.md [Substrate: Multiple Actors Per Worker](https://docs.google.com/document/d/1yaagfSgh6Y7Qxq4gOG0GGh45yVk1VJsQv1Aa3W_O6RA/edit?tab=t.0) outlines an incremental approach to enabling multiple actors per worker. Here is a markdown conversion of the current iteration of the doc, but it is missing comments on the doc https://gist.github.com/BenTheElder/1fd8d7b456c66999594b791b2f96fc34 https://github.com/agent-substrate/substrate/issues/44 & https://github.com/agent-substrate/substrate/issues/793 are some early issues that previously asked about the concept. ---- At a very high level the plan is to make these changes incrementally. I have a working version but it's an unreasonably large diff at this stage of the project. The doc outlines some of those incremental steps. I'm going to start filing some of the PRs that aren't strictly blocked on it today, and a **draft** of the API changes for review.
Activity
Ateom child reaper (#1293)
ateclient: spread RPCs over every ateapi replica (#1319)
multi-actor worker API (#1283)
8 remaining items
ateomnet: replace stale named namespaces (#1682)
ateom: pluralize the discovery read for multi-actor workers (#1644)
e2e: copy the source pool's worker resources (#1691)
e2e: give the parking suite its own fixture (agent-substrate#1735)
per sandbox networking (agent-substrate#1689)
BenTheElder commentedon Sep 23, 2026
#1689 was the main outstanding pre-req, prepping a big PR to cap this off.
BenTheElder commentedon Sep 24, 2026
This has baseline support and will be in v0.2.0.
We know we need to do follow-ups.
multi actor worker support (agent-substrate#1836)