Repository navigation
Description
Summary
AX 8d2ccf3 (current main) cannot create tasks on Agent Substrate after v0.5.0. With agent-substrate/substrate@3d3b929 (2026-10-18), every Task fails at template creation. There is also no way to run tasks on a non-gVisor sandbox class such as microvm.
What changed in Substrate
In pkg/proto/ateapipb/ateapi.proto, ActorTemplate changed in four ways:
sandbox_config(field 6) was removed. The WorkerPool now decides the sandbox class, and templates choose a pool throughworker_selector.resourcesis required. cpu and memory limits are both mandatory.- Container images must be pinned by digest.
- The Go module moved from
github.com/agent-substrate/substratetogo.ate.dev/substrate.WakeupProbeandHttpGetActionwere renamed.
Repro
- GKE 1.36; Substrate
3d3b929installed withhack/install-ate.sh --deploy-ate-system. - AX
8d2ccf3deployed withmake deploy. - Apply a minimal Task:
apiVersion: ax.io/v1alpha1
kind: Task
metadata:
name: smoke1
atespace: default
spec:
resources:
limits:
cpu: "2"
memory: "4Gi"ax-server logs:
could not create custom ActorTemplate, falling back to default template
error="creating actor template default/smoke1-tmpl-49b5e690: rpc error: code = InvalidArgument
desc = actor_template: Invalid value: unknown field with protobuf tag 6"
direct reconcile error on create task task=smoke1
error="ensuring actor: creating actor default/smoke1: rpc error: code = FailedPrecondition desc = actor template not found"
Once field 6 is gone, Substrate rejects the template again unless resources is set and the image has a @sha256: digest. The default gcr.io/ax-substrate/ate-images/ax-task-runner is tag-only.
Related
- chore(substrate): bump github.com/agent-substrate/substrate to v0.5.0 #484 bumps to
v0.5.0. That release still hassandbox_config, so this break com 75DD es with the next bump. - feat(controller): apply Task resource limits to the ActorTemplate #405 copies Task limits onto the template. That covers point 2.
- Release hygiene: publish images with each release and state which Substrate release AX works with #487 asks AX to state which Substrate release it supports; this issue is an example of why.
- Default snapshot bucket is a hard-coded Google test bucket; AX_SNAPSHOTS_BUCKET override is undocumented #372 (hard-coded snapshot bucket) and Quick start never creates or mentions a WorkerPool, so the first Task fails with ResourceExhausted #437 (quick start never creates a WorkerPool) came up on the same install.
Possible fix
BuildActorTemplate in internal/substrate/client.go would:
- drop
SandboxConfig; - set
Resourcesfrom the Task's limits; - set
WorkerSelectorfrom configuration, so an operator can route tasks to a pool of a given class (for example,ax.dev/pool=microvm).
We're running a minimal version of this against Substrate 3d3b929: gethamster@43fd8d5. It uses an AX_WORKER_SELECTOR env var, falls back to requests and then 2 CPU / 4Gi for limits, and passes go test ./....
We'd be glad to send a PR, either on top of #405/#484 or as a standalone change, once you confirm the direction. In particular: should the worker selector be a server flag, a per-Task field, or both?
Activity
rakyll commentedon Oct 19, 2026
cc @siyuanfoundation