@looptail/cli

@looptail/cli

Verify a Looptail trail from your terminal: hash chain and Ed25519 signatures. No dashboard required, no trust required.

npx @looptail/cli verify --app support-agent --since 24h

✔ 1,204 loop events
✔ chain intact · signatures valid

Any modification, deletion, or reorder of past records breaks the chain:

✖ trail failed verification (support-agent)
  event 2 (evt_01J2ZK…): hash mismatch (record was modified)

Usage

looptail verify [--app <name>] [--trail-dir <dir>] [--since <window>] [--anchors] [--json]
looptail export [--app <name>] [--trail-dir <dir>] [--out <file.zip>]

• --app — app whose trail to use (defaults to the only app in the trail dir)
• --trail-dir — trail directory (default: LOOPTAIL_TRAIL_DIR or ./.looptail)
• --since — count events in a recent window (30m, 24h, 30d). The full chain is always verified — integrity is global.
• --anchors — also fetch the server's signed chain-head receipts and check them: receipt signatures must verify against the server key, and every anchored head must exist in the local chain (a missing head means the local file lost or rewrote events the server witnessed). Needs LOOPTAIL_API_KEY; endpoint via --endpoint or LOOPTAIL_ENDPOINT (default https://ingest.looptail.ai).
• --json — machine-readable output (verify)

export writes a dated, self-verifying evidence pack: the complete chain byte-for-byte, a manifest (head hash, writer keys, SHA-256 of the trail), and VERIFY.md — instructions the recipient can run without trusting you. It refuses to export a chain that fails verification.

Exit codes: 0 ok · 1 verification failed · 2 usage error.

Works on trails written by any spec-conformant SDK — looptail (Python) and @looptail/sdk (TypeScript) — per spec/trail-format.md.

Docs: looptail.ai/docs · License: Apache-2.0