Repository navigation
Local development #526
Description
Trying AX locally takes a lot of setup. You need a Kubernetes cluster with Agent Substrate installed, plus Go, ko, a container registry and make deploy. That's a high bar for someone who just wants to run a task, and it slows down contributors who want to test changes against real sandboxes.
Our e2e test setup already does most of this on Kind, but it's built for tests. It wipes the database on every run, uses a test runner image, and writes a separate kubeconfig that ax doesn't pick up.
Proposal
Add local cluster management commands:
ax local start # create or reuse the cluster, install Substrate and AX
ax local status # show what's running and whether it's healthy
ax local stop # stops the clusterAfter ax local start, everything should just work:
ax local start
ax ap
9143
ply -f examples/task.yaml
ax ssh task123 -- ls /workspaceax local start should:
- Check for Kind and a container runtime, either Docker or Podman. Use whichever is available, or the one picked with a flag such as
--runtime=podman. - Create or reuse the Kind cluster.
- Install Substrate, Postgres and
ax-server. - Keep data between runs.
- Switch the kube context so
axfinds the server.
Activity
rakyll commentedon Nov 1, 2026
Duplicate of #543.