II.
Term JSON
Structured · liveterm:invocation-mode
Invocation Mode json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "term:invocation-mode",
"_kind": "Term",
"_file": "terminology/terms/terms-articles-and-refs.yaml",
"_cluster": "terminology",
"attributes": {
"displayName": "Invocation Mode",
"kind": "concept",
"description": "Selects where a harness subprocess runs. agent-mux defines four\nmodes — local (default), docker (`docker run --rm -i ...`), ssh\n(`ssh ... -- 'cd <cwd> && cmd ...'`), and k8s (`kubectl exec -i\n<pod> -- ...`). The adapter contract emits a mode-agnostic\nSpawnArgs which a pure transform rewrites for the chosen host.\nSource: docs/agent-mux/reference/13-invocation-modes.md.\n"
},
"outgoingEdges": [
{
"from": "term:invocation-mode",
"to": "term:agentic-loop",
"kind": "related_to",
"attributes": {}
}
],
"incomingEdges": []
}