runspec-linux
Linux system-administration runnables (plus Python-venv management, crontab,
filesystem, and the cross-platform web/TLS/API probes) for
runspec. pip install it into a venv and
the runnables are discoverable by runspec local, runspec serve (MCP), and
runspec-console.
All runnables emit JSON on stdout. Read-only runnables are autonomy = "autonomous"; state-changing ones are autonomy = "confirm". The privileged
runnables declare run_as = "root", so runspec-console escalates them via
sudo — run enable-passwordless-sudo once to install a visudo-validated
/etc/sudoers.d drop-in so they run without a password prompt.
Install
pip install runspec-linux
Runnables
| Group | Runnables |
|---|---|
| System | system-info, disk-usage, check-memory, cpu-info, pressure |
| Processes | list-processes |
| Services | list-services, check-service, restart-service, service-detail, failed-units |
| Logs | tail-log, search-log, journalctl |
| Network | ping-host, check-port, show-connections, trace-route, route-table, socket-stats, dns-config, open-ports |
| Kernel params | get-sysctl, set-sysctl |
| Files | find-large-files, backup-files, owning-package |
| Sessions | last-logins, who |
| Containers | list-containers, container-logs, restart-container |
| Packages | list-packages, list-upgrades, upgrade-packages, install-package, remove-package |
| Power | reboot-host |
| Sudo bootstrap | enable-passwordless-sudo |
| Python venvs | create-venv, install-into-venv, configure-pip |
| TCP | nc-command |
| Commands | which |
| Cron | cron (multi-verb: list/add/remove/clear) |
| Filesystem | filesystem (multi-verb, backed by runspec-fs-core) |
| Web / TLS / API | cert-check, cert-chain, tls-info, http-check, http-headers, redirect-trace, dns-lookup, api-spec |
The package-management runnables auto-detect apt / dnf / yum / zypper / pacman.
The web/TLS/API probes are pure HTTP (shared with runspec-windows via
runspec-webops-core) and run anywhere.
system-info
list-upgrades
check-port --host db-01 --port 5432
cert-check --url https://internal.example.com
Python venvs
create-venv, install-into-venv and configure-pip take a per-invocation
--run-as <user> (+ --become-method sudo|su) rather than a declarative
run_as, so the service account that owns a shared venv is chosen per call:
create-venv --python /usr/bin/python3.12 --dest /opt/venvs/ops --run-as svc-ops --group ops
install-into-venv --venv /opt/venvs/ops --package "runspec-linux==0.13.2" --run-as svc-ops
Public Python API
The pure logic lives in runspec-linux-core — no
runspec dependency, no runspec.toml, no entry points (so it surfaces no
runnables). A corporate wrapper package that only wants a helper should depend
on the core alone:
from runspec_linux_core import nc_send, system_info, install_into_venv
The helpers are also re-exported from runspec_linux for back-compat. Core
helpers return plain data and raise (ToolNotFoundError / CommandError) on
failure; the runnable wrappers catch these to render the CLI/agent behaviour.
Development
python -m venv .venv && . .venv/bin/activate
pip install -e ".[dev]"
ruff check . && ruff format --check .
pytest
1 maintainer
Release files for runspec-linux 0.14.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| runspec_linux-0.14.0.tar.gz | 34.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| runspec_linux-0.14.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.4 kB
Release files / runspec_linux-0.14.0.tar.gz
| Download URL | runspec_linux-0.14.0.tar.gz |
|---|---|
| Size | 34.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c4b8409befbb7737ed9372ca774429428b1154f371003fca2043472ba3b75f6
|
|
BLAKE2b-256 checksum How to use checksums |
f77a708084495b1fe66b428f6e23fde0fd612845def89bccc432159dfd108f4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logRelease files / runspec_linux-0.14.0-py3-none-any.whl
| Download URL | runspec_linux-0.14.0-py3-none-any.whl |
|---|---|
| Size | 31.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e72245020e90711239b15ed81d89ec4deb8dd41af77b60bd04e930cd092e5ac3
|
|
BLAKE2b-256 checksum How to use checksums |
23ac66a345d40fd3eb211c7dc187fc076392d11da8f54ab7e7c06e0be450adf2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency log
