Piper – DevOps copilot where the LLM picks typed actions, not shell
PIPER is a terminal-first, LLM-driven DevOps copilot designed to enhance safety and efficiency in operations. It proposes actions from a fixed catalog, which are validated before execution, ensuring human oversight for any changes. The tool aims to assist developers and DevOps engineers by providing a reliable interface for managing infrastructure without the risk of unintended mutations.
- ▪PIPER uses a deterministic code validation process to ensure safety in DevOps tasks.
- ▪The LLM only proposes actions from a closed catalog and does not execute commands directly.
- ▪Human approval is required for any actions that could mutate the system.
Opening excerpt (first ~120 words) tap to expand
PIPER DevOps at the speed of thought. A terminal-first, LLM-driven DevOps copilot that is safe by construction — the LLM proposes, deterministic code validates, the human approves anything that mutates. Why · Quick start · The gate · Catalog · Knowledge base · Security ImportantThe LLM never executes anything. It only picks an action from a fixed catalog. PIPER then validates the choice and runs the command on your own machine through a single audited executor. The LLM is a planner, not a shell. This is the entire product. Demo PIPER pulls the relevant runbook from its knowledge base, runs read-only diagnostics over SSH, finds the planted issues, proposes fixes — and refuses to apply them, because M1 is read-only.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.