Module selector 

Shared agent-input shape for agents spawn and agents message.

Both commands address an agent the same three ways:

• Ref — a concrete agent definition: a remote-path string (--agent), inline JSON (--agent-inline), a JSON file (--agent-file), or Python producing the JSON (--agent-python-inline / --agent-python-file). File/Python variants travel UNRESOLVED on the wire; the CLI resolves them into a typed agent at execution time.
• Tag — --agent-tag <name>, resolved against the tags DB at call time: BOUND yields the live agent_instance_hierarchy (historic instance), GROUPED yields the group’s stored agent spec (fresh spawn that upgrades the group on first conduit read), ABSENT is an error.
• Instance — --agent-instance <leaf> plus optional --parent-agent-instance-hierarchy (the CLI substitutes its own Config.agent_instance_hierarchy when omitted): an existing agent instance, resumed via its stored session + continuation.

Structs

AgentSelectorArgs

Required agent-selector group: exactly one of the seven selector flags must be set. --parent-agent-instance-hierarchy rides OUTSIDE the group (it modifies --agent-instance rather than competing with it).

Enums

AgentRef

Wire form of a direct agent definition. Resolved carries the typed inline-or-remote spec (the --agent <ref> string is parsed into Resolved(Remote(..)) at argv-parse time); the other variants defer IO / Python execution to the CLI handler.

AgentSelector