Skip to content

Commands and Capability Index

Execution commands

Command	Purpose	Typical use case
`rauto exec`	Execute a raw command	Fast checks and troubleshooting
`rauto template`	Render and execute a stored template	Parameterized configuration delivery
`rauto flow`	Execute an interactive command flow template	`copy scp:`, installers, confirmation flows
`rauto upload`	Upload a local file over SFTP	File delivery to Linux hosts
`rauto tx`	Run a rollback-aware transaction block	Compact single-target changes
`rauto tx-workflow`	Execute a workflow JSON file	More complex single-target transactions
`rauto orchestrate`	Execute a multi-device plan	Batch rollout, staged delivery, and controlled release

Service commands

Command	Purpose
`rauto web`	Start the local web console
`rauto agent`	Start a managed agent and connect it to `rauto-manager`

Management commands

Command group	Purpose
`rauto device ...`	Inspect, copy, and diagnose device profiles
`rauto connection ...`	Manage saved connections and connectivity tests
`rauto inventory ...`	Manage groups and variable resolution previews
`rauto templates ...`	Manage command templates
`rauto flow-template ...`	Manage command flow templates
`rauto history ...`	Inspect execution history for saved connections
`rauto blacklist ...`	Manage blocked command patterns
`rauto backup ...`	Backup and restore runtime data
`rauto replay ...`	Replay JSONL recordings

Key design points

The default profile is `linux`

If you are connecting to a network device, remember to explicitly set --device-profile.

Many advanced features work best with saved connections

As templates, transactions, and orchestration get more complex, --connection <name> becomes the more reliable way to work.

Command templates, command flow templates, saved connections, and custom profiles are all stored by default in ~/.rauto/rauto.db.

Recording is a first-class feature

Most execution commands support recording and replay, making rauto not just an executor but also an auditable and replayable operations system.

Typical command paths

From ad-hoc execution to reusable templates

rauto exec "show version" --host 192.168.1.1 --username admin --password secret --device-profile cisco
rauto connection add core-01 --host 192.168.1.1 --username admin --device-profile cisco
rauto template show_version.j2 --connection core-01

From local usage to centralized management

rauto web --bind 127.0.0.1 --port 3000
rauto agent --manager-url http://manager:3000 --report-mode http --agent-name edge-01 --agent-token <token>

Further reading