nemo-try-agent

name	nemo-try-agent
description	Invokes an existing NeMo Platform agent through a named deployment or directly from a local agent YAML config. Use to try, test, or query an agent and inspect its response.
triggers	["nemo-try-agent","ask my agent","ask my NeMo agent","try the agent","test it out","test support agent with real question","query my agent","what does my agent say","send to the agent","try my nemo agent","invoke deployed agent","query running deployment","invoke local agent config","query local agent config","invoke legacy NAT workflow","test agent and show raw output"]
not-for	["nemo-build-agent (use to deploy an agent before querying)","nemo-skill-selection (use to dispatch when intent is unclear)","nemo-status (use for read-only platform health)"]
preconditions	["nemo_setup_complete","workspace_exists","provider_registered","agents_plugin_available","agent_config_exists"]
compatibility	nemo-platform >= 0.1.0; requires agents plugin and either a local agent YAML config or a running platform with a deployed agent; no destructive ops; safe under any sandbox.
maturity	active
license	Apache-2.0
user-invocable	true
allowed-tools	["Bash","Read"]

NeMo Platform try-agent

Invoke an existing NeMo agent through a deployment or directly from a local YAML config. Announce the target before sending. Never invoke silently.

Pre-flight

Choose the invocation mode from the user's target:

• Local one-shot: the user provides an agent.yaml or legacy NAT workflow YAML path. Read the config format and model settings before deciding whether Platform readiness is required:
  • A Platform-managed nemo-agents-spec-v1 config invokes Fabric directly and does not require Platform readiness.
  • A legacy NAT config requires Platform readiness when any openai or nim LLM omits base_url; local invocation injects the Platform IGW URL for those entries.
  • A legacy NAT config whose applicable LLMs all provide explicit base_url values may invoke those endpoints directly without Platform readiness.
• Deployed agent: the user names a deployment or asks to use an already deployed agent. Preserve the active CLI context and confirm the target Platform is reachable by listing deployments:

.venv/bin/nemo agents deployments list 2>/dev/null || { echo "PLATFORM_UNREACHABLE"; exit 1; }

When the user explicitly selects a local Platform, override any remote CLI context for the current shell and add local process and health checks before listing deployments:

export NMP_BASE_URL=http://localhost:8080
lsof -iTCP:8080 -sTCP:LISTEN >/dev/null 2>&1 || { echo "PLATFORM_DOWN"; exit 1; }
curl -sS --connect-timeout 2 --max-time 5 "$NMP_BASE_URL/health/ready" -o /dev/null -w "%{http_code}\n" 2>/dev/null | grep -q "^200$" || { echo "PLATFORM_WEDGED"; exit 1; }
.venv/bin/nemo agents deployments list 2>/dev/null

Do not use nemo services status for the local process check; it can report stale "running" state from held locks after the process has died.

Require these checks for a deployed invocation and for a local NAT invocation that depends on injected Platform IGW routing. If or , route to and stop. If , route to and stop. Do not require the checks for Platform-managed Fabric local invocation or a NAT config with directly usable explicit endpoints.