SysKnife
Infrastructure · tested 2026-08-19 · re-test due 2026-11-19 · by the Hlido desk, not the vendor
In short: A Linux sysadmin co-pilot built around the right safety primitive: the AI proposes typed actions, never shell strings, and a privileged daemon executes only what you approve.
Quick answer
SysKnife scores 81/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-19). STEADY (81) for a system-level agent co-pilot whose core design is a genuine safety architecture (typed actions not shell strings, privilege-separated brain/shell/daemon, mandatory human approval, Ed25519 hash-chained au Pricing: Open source (free entry point documented).
SysKnife turns a plain-language request into a typed plan — named actions with formal risk levels (Low read-only, Medium reversible, High irreversible) — that you review and approve before a root daemon executes it step by step with live output and automatic rollback on failure. The architecture is the point and it is well-drawn: an unprivileged brain talks to the LLM and can only propose typed actions; an approval-gate shell shows you the plan and collects consent; a locked root daemon is the only thing that touches the system, and only after an approved plan. Every execution is Ed25519-signed and hash-chained into an immutable audit trail. This directly answers the failure mode of pasting an LLM's shell command and finding out what it did afterward. MCP is presented as the primary path (npx sysknife-setup wires up Claude Code, Cursor, Codex CLI), with a fully-supported CLI and a distant-third experimental GUI. The claimed evidence base is substantial and specific: 190 typed actions, 1,759 Rust tests plus 72 frontend tests, MIT-licensed, with committed live-VM story runs for Ubuntu 22.04/24.04/26.04 at 79/79 and honest gates flagged for Fedora Atomic and plain Fedora. SysKnife is also framed as the reference implementation of LACS, a CC0 protocol. Hlido reviewed the documentation site, not a running daemon, so the audit chain, rollback and story-run results are described-and-cited rather than reproduced here — but the trust-boundary design is exactly what system-level agent tooling should look like.
Why STEADY
STEADY (81) for a system-level agent co-pilot whose core design is a genuine safety architecture (typed actions not shell strings, privilege-separated brain/shell/daemon, mandatory human approval, Ed25519 hash-chained audit, automatic rollback), backed by a specific evidence base (190 actions, 1,759+ tests, committed multi-release VM story runs) and MIT-licensed — held at low-medium confidence because Hlido reviewed the docs surface, not a live daemon, so the audit chain and story runs are cited rather than reproduced. Not VITAL absent hands-on verification of the privileged execution path.
What we saw
4 screenshots captured by the Hlido engine during the reviewed run (run-349042e4bb09dfd2-lacs-project-github-io). Our own captures — not vendor marketing material.
What it does well
- Correct core safety primitive: the LLM emits typed actions with risk levels, never raw shell strings, and cannot itself touch the system
- Clean privilege separation — unprivileged brain (proposes) / user shell (approval gate) / locked root daemon (executes) — with human approval mandatory
- Immutable accountability: every execution is Ed25519-signed and hash-chained; automatic rollback on high-risk failure
- MCP-first (npx sysknife-setup for Claude Code / Cursor / Codex) with a first-class CLI; runs local models via auto-detected Ollama with no API key
- Specific, checkable evidence base — 190 typed actions, 1,759 Rust + 72 frontend tests, MIT, and committed 79/79 live-VM story runs across three Ubuntu LTS releases, with Fedora honestly marked experimental
What it fails at
- Surface-only review — Hlido read the documentation, not a running daemon, so the audit chain, rollback and story-run pass rates are cited, not reproduced here
- Fedora support is partial by the project's own admission (Atomic gated on a Silverblue run; plain Fedora experimental until the dnf action family ships)
- A source build pulls ~400 crates and takes ~7–12 minutes; running it means a root daemon on your system
- The desktop GUI is explicitly the least-maintained surface — reach for MCP or CLI
Best for
- Engineers who want an AI Linux co-pilot with real guardrails — preview, approval, rollback and a signed audit trail
- Teams that need an accountable record of every system change an agent made
- Ubuntu/Debian users wanting MCP-driven administration from Claude Code / Cursor / Codex
Not recommended for
- Plain-Fedora or non-Ubuntu users needing full action coverage today
- Anyone unwilling to run a privileged (root) daemon
- Users wanting a polished GUI-first experience
Pricing & access
- ModelOpen source
- Free entry pointYes — a free tier or open-source edition is documented
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-18.
Related agents
Agent relevance
CLI MCP Behavioral-testable
Agentic-Commerce Readiness 57/100 · INTEGRABLE
Independent readiness for agent delegation & transaction. How it’s scored · check live
`npx sysknife-setup` wires the MCP server into Claude Code / Cursor / Codex CLI; the agent proposes typed actions in chat, the user approves in a terminal, and a root daemon executes with a one-time receipt. A first-class CLI offers the same loop.
Agent-friendly score: 9/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
- Correct core safety primitive: the LLM emits typed actions with risk levels, never raw shell strings, and cannot itself touch the system — source (2026-08-19) verified
- Clean privilege separation — unprivileged brain (proposes) / user shell (approval gate) / locked root daemon (executes) — with human approval mandatory — source (2026-08-19) verified
- Immutable accountability: every execution is Ed25519-signed and hash-chained; automatic rollback on high-risk failure — source (2026-08-19) verified
- MCP-first (npx sysknife-setup for Claude Code / Cursor / Codex) with a first-class CLI; runs local models via auto-detected Ollama with no API key — source (2026-08-19) verified
- Hands-on runtime behaviour (executing the tool / a live task) — source (2026-08-19)



