- name
- rauto-usage
- description
- Execute rauto directly for the user: run device commands, template execution, tx block, tx workflow, multi-device orchestration, replay, backup/restore, and connection/profile/template/history operations. Trigger on requests like run command for me, execute on device, check history, run workflow, orchestrate multiple devices, apply staged rollout, use inventory/groups, diagnose profile, manage templates/profiles/connections, replay records, or restore backup.
Rauto Usage
Execute rauto operations directly for users whenever possible. Do not default to tutorial-style answers.
Core Mode
Prefer action-first behavior:
- Parse user goal and classify it as read-only or config-changing.
- For read-only operations, run the relevant
rautocommand immediately. - For config-changing operations, prefer
tx/tx-workflow/orchestratewith rollback-aware planning. - If commands are generated by the agent, ask for human confirmation before execution.
- Return key results (not raw noise), plus command used.
Execution Rules
- For read/query requests, execute immediately:
- examples: device list, connection list, history list, templates list, replay --list.
- For config-changing requests, prefer rollback-capable execution:
- single block: tx - multi-step/multi-resource: tx-workflow - multi-device staged rollout: orchestrate
- For generated change commands, do not execute immediately:
- show planned command(s), rollback strategy, and require user confirmation.
- For explicit read-only commands (for example
show), tx/workflow is not required. - Resolve connection in this priority:
- explicit command args > --connection <name> > ask for missing fields.
- Do not ask the user to manually run commands if agent can run them.
- Summarize outputs with important fields:
- target, mode, success/failure, key errors, next action.
Risk Guardrails
Require explicit user confirmation before destructive actions:
rauto backup restore ... --replace- profile/template/connection delete operations
- tx/workflow execution that changes config when user intent is ambiguous
Additional safety requirements for config changes:
- Prefer
tx/tx-workflow/orchestratewith rollback-aware planning over direct apply patterns. - Run/offer
--dry-runfirst for workflow-based changes. - For
orchestrate, review target scope,fail_fast, concurrency, and rollback boundary before execution. - Never auto-run agent-generated change commands without confirmation.
- Include rollback path in the proposal before execution.
If user explicitly asks to execute destructive action, proceed.
Missing Input Strategy
Ask only for missing must-have fields:
- For
exec/template/tx/tx-workflow/orchestrate/connection test:
- need either full host credentials or usable --connection.
- For
replay:
- need record file path or JSONL source.
- For history queries:
- need connection name.
Response Format
When command is executed, report:
Operation: what was runCommand: exact rauto commandResult: key output summaryNotes: risk, errors, or follow-up actions
Navigation (Load References On Demand)
- Agent execution decision tree and command templates:
references/agent-execution.md - Full CLI command cookbook:
references/cli.md - Runnable multi-device orchestration JSON templates (EN):
references/orchestration-json-template.md - Multi-device orchestration pre-flight review:
references/orchestration-risk-check.md - Runtime storage paths:
references/paths.md - Troubleshooting and recovery:
references/troubleshooting.md - End-to-end operation scenarios:
references/scenarios.md - English Q/A examples:
references/examples.md - Runnable workflow JSON templates (EN):
references/workflow-json-template.md - Web tab/card mapping (only when user asks for Web operations):
references/web.md