r1ctl Features
command groups, examples, and operational guardrails
r1ctl Features
This page maps r1ctl features to practical command groups and usage patterns.
1) Node and network visibility (get)
r1ctl get nodesr1ctl get nodes --peered --wider1ctl get supervisors --wider1ctl get commsr1ctl get eth <node_addr>r1ctl get networks
Use this group first for troubleshooting connectivity, peering, and active fleet status.
2) App inspection and availability
r1ctl get apps --node <node_addr_or_eth> --wider1ctl get avail <node_eth_addr> --start <epoch> --end <epoch>r1ctl get avail <node_eth_addr> --start <epoch> --end <epoch> --rounds 3
Notes:
- availability checks use oracle-response tooling in CLI implementation;
--jsonmode is available onget availandget apps.
3) Local client configuration (config)
r1ctl config showr1ctl config addrr1ctl config network --set mainnetr1ctl config network --set testnetr1ctl config alias --set my-dev-aliasr1ctl config reset
Use these when switching environments, validating address context, or resetting local state.
Current CLI network setter accepts mainnet and testnet.
4) Node control commands
r1ctl restart <node>r1ctl restart <node> --ignore-peeringr1ctl shutdown <node>
These commands are operational actions, not diagnostics. Verify target and authorization before executing.
5) Rollout and maintenance
r1ctl oracle-rolloutr1ctl oracle-rollout --skip-seedsr1ctl oracle-rollout --skip-oraclesr1ctl oracle-rollout --skip-workersr1ctl oracle-rollout --timeout
oracle-rollout includes explicit confirmation flow and group sequencing in current CLI logic.
6) Inspection and updates
r1ctl inspect <node> --wider1ctl updater1ctl update --quiet
Use inspect for focused node diagnostics and update for package maintenance.
Ground truth references
Primary:
Supporting:
Notable date
- Reviewed on February 17, 2026.
Next steps
- Back to r1ctl.