Use casesCLI tools

Interactive diagnostic CLIs

The REPL for probing live systems, mock mode for repro scripts, and secrets so pasted customer data does not land in shell history.

The problem

Support engineers need a command that takes an id, fetches context, and asks a model "what went wrong?" Copy-pasting into ChatGPT leaks customer data; a Python REPL prints secrets to stdout; neither is auditable.

Why Ecko

ecko repl
Probe APIs and data structures interactively. Same language as the production handlers, so snippets from the REPL paste into fixes.
secret inputs
Wrap pasted payloads in secret before logging or sending to ai. Accidental print stays redacted.
Traceable runs
Even ad-hoc CLI invocations can set ECKO_TRACE so a support session leaves the same JSONL audit trail as production.

In practice

diag.ecko
fn investigate(ticket: secret(str)) {
  ai "Likely root cause" from reveal(ticket)
}

# ECKO_TRACE=support.jsonl ecko diag.ecko CASE-4821

Further reading

Related cases

All 32 use cases →

Try it on your workload.

Install Ecko Open the playground