wentf9/xops-cli
Developer toolsThis page was translated automatically. Technical details may differ from the original. View the original
A high-performance, cross-platform operations CLI tool based on Go. Provides host management, SSH connections, file transfers, batch execution, and Playbook task orchestration. It can also connect to AI clients via Model Context Protocol (MCP) for configuration of operation approval and auditing.
Overview
Monobinary, zero-remote dependency modern terminal operations and AI automation toolbox SSH / SFTP · Terminal TUI · Offline encrypted credential library · Batch parallel execution · YAML Playbook · Controlled MCP services and Agent Skills 📖 Online Documentation · 🚀 Quick Start · ⌨️ Command Reference · 🔧 Troubleshooting · English In daily operations and infrastructure management, do you often switch between these tools: - Handwriting ~/.ssh/config, or risking sshpass to save passwords and leaving plaintext passwords in Shell history? - When facing dozens of machines, do you feel that building an Ansible/Python environment is too heavy, and you only want a single file binary to run commands, transfer files, and perform state convergence? - When connecting to Alpine containers (without Bash), Windows OpenSSH (CMD / PowerShell), or fish/zsh nodes, the scripts always throw errors due to incompatible Shell dialects? - Want AI assistants like Claude, Codex, Cursor to help you inspect and maintain servers, but worry that if you grant permissions, the AI might accidentally execute high-risk commands? These capabilities are consolidated into **: zero remote dependencies, authentication is encrypted locally by default, automatic detection of target shell environments, and natively provides ** and _ with risk guardrails and approval auditing. (Requires Go 1.26+, Makefile natively supports Linux, macOS, and Windows): XOps decouples network address (), authentication identity () from connection node (), and manages it so that the same IP can be associated with multiple accounts with different permissions: - : When ssh, sftp, scp, exec first connect to a new host, the node is saved only after SSH handshake and authentication are successful; Connection timeouts or password errors will not leave junk records. - : Single connection can add --remember never to disable password memory, or set credential.remember_prompted: ask | in configuration never。 For offline addition or import, you can use --skip-verify (or --no-probe to skip Shell probes). - For details, see: Host and Identity · Credential Storage · Offline Credential Library · Credential Migration Write a declarative Playbook (deploy.yaml) using YAML to implement idempotent deployment:
Overview (machine translated)
A modern terminal operations and AI automation toolbox with single binary and zero remote dependence SSH / SFTP · Terminal TUI · Offline encrypted credential library · Batch parallel execution · YAML Playbook · Controlled MCP Services and Agent Skills
📖 Online Document · 🚀 Quick Start · ⌨️ Command reference · 🔧 Troubleshooting · English
In daily operations and infrastructure management, do you often switch between these tools:
- Handwriting
~/.ssh/config, or riskingsshpassto save passwords and leaving plaintext passwords in Shell history? - When facing dozens of machines, do you feel that building an Ansible/Python environment is too heavy, and you only want a single file binary to run commands, transfer files, and perform state convergence?
- When connecting to an Alpine container (without Bash), Windows OpenSSH (CMD / PowerShell), or fish/zsh nodes, the script always throws errors due to incompatible shell dialects?
- Want AI assistants like Claude, Codex, Cursor, etc. to help you inspect and maintain servers, but worried that unlocking permissions might cause AI to accidentally execute high-risk commands?
XOps CLI consolidates these capabilities into a cross-platform Go binary file: zero remote dependencies, locally encrypted credentials by default, automatic detection of target shell environments, and native MCP server and AI Agent Skill with risk guardrails and approval auditing.
⚡ Get Started in 30 Seconds
Compiled from source code (Requires Go 1.26+, Makefile natively supports Linux, macOS, and Windows):
✨ Why Choose XOps CLI?
| Pain Points | XOps CLI Solutions |
|---|---|
| Password management is complicated and insecure | Verify once, remember encryption: After the first connection authenticates, the login password, private key password, and sudo/su password are automatically encrypted and stored locally on ~/.xops/credentials/ (native Keychain, [T5]] or custom helper are also supported. Plaintext passwords will never appear in YAML configuration. |
| Heterogeneous environment and bash-less container errors | Zero remote dependency + automatic shell probe: By default, server passthrough mode does not depend on remote pre-installed Bash; When adding or connecting nodes for the first time, the same SSH connection is reused, automatically detecting outer dialects (posix/fish/cmd/powershell) and available interpreters (bash/sh/zsh/fish/powershell/pwsh/cmd), Alpine and Windows OpenSSH are ready to use out of the box. |
This page was translated automatically. Technical details may differ from the original.
Recommended Tools
Try a different keyword or remove a filter.
Install
npx skillfish add wentf9/xops-cli