[substrate] Interactions actor reads harness config from ax.yaml - #302
Merged
Conversation
zbl94
approved these changes
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, the Antigravity Interactions harness always use default value on substrate deployment. Its config in ax.yaml is only used by local path.
Changes
AX_CONFIG_CONTENT, Antigravity Interactions harness reads its deploy config (agent, state_dir) from ax.yaml on the substrate/actor path, with fallback to built-in defaults.manifests/ax.yaml. It's used by both the controller ConfigMap and the actor's env var.Tested
Deployed and run on substrate. Both SDK and Interactions work.