kilolock.dev

CLI Overview

Kilolock currently exposes three main binaries:

• kl for operator and developer workflows
• kld for the backend/runtime server
• klc for the control-plane server

The CLI model is intentionally incremental.

Most common usage

• Use Terraform or OpenTofu with a standard HTTP backend.
• Use kl query, kl status, kl history, and related commands for visibility.
• Adopt scoped or orchestrated workflows only when they solve a real coordination problem for your team.

The command examples that matter most

Query what Terraform wrote

kl query "SELECT type, COUNT(*) FROM resources GROUP BY type ORDER BY 2 DESC"
kl query resource --address time_sleep.slow_a
kl query history --address time_sleep.slow_a

Inspect state without opening a state blob

kl status example
kl history example

Repair or roll back a specific resource

kl rollback resource --address time_sleep.slow_a --to @1
kl apply abort --state example --latest

Run scoped workflows

kl plan -f slow_a.tf -o slow-a.plan.json
kl apply -f slow_a.tf --confirm-scope

These are the kinds of workflows that make Kilolock more than “just another backend.”

Related docs

• Standard HTTP Backend
• Querying State with kl
• Status, History, and Repair
• Scoped and Advanced Apply
• Protocol Reference