Skip to main content

Record every AI decision as a signed, append-only trail. Every loop leaves a tail.

Project description

looptail

Record every AI decision as a signed, append-only trail. Every loop leaves a tail.

pip install looptail
import looptail

looptail.init(app="support-agent")

@looptail.trail
def handle_ticket(ticket):
    ...

# report an outcome signal when you learn how it went
looptail.outcome(looptail.last_event_id(), csat=5)

Every call becomes a hash-chained, Ed25519-signed loop event appended to .looptail/support-agent.jsonl. Nothing is edited in place; any modification, deletion, or reorder of past records is detectable:

npx @looptail/cli verify --app support-agent

✔ 2 loop events
✔ chain intact · signatures valid

Or from Python: looptail.verify_trail().

The whole loop, CLI-first

looptail-evals run --rubric rubrics/refund-policy.json --app support-agent
looptail-issues cluster --app support-agent
looptail-improve propose --app support-agent --issue refund-policy/v1/criterion-0 \
    --prompt-file prompts/support.txt
looptail-improve replay --app support-agent --proposal prop_... \
    --cases regression.jsonl --runner myapp.replay:run --rubric rubrics/refund-policy.json
looptail-improve approve --app support-agent --proposal prop_... --apply

Evaluators score recorded events against your rubrics with an LLM judge (pip install "looptail[anthropic]" or [openai]); failing verdicts cluster into tracked issues; the improve loop drafts a patch, replays your regression set, and gates approval on a passing replay. Every step lands in the trail as a signed event. Guide: looptail.ai/docs/improve.

How it works

  • A signing key is created on first use at ~/.looptail/signing-key (override with LOOPTAIL_SIGNING_KEY, hex seed).
  • Events follow the open trail format — spec/trail-format.md — and are verifiable by any implementation, including the JS CLI.
  • The local trail is the source of truth. With an API key (looptail.init(app=..., api_key=...) or LOOPTAIL_API_KEY), events also sync to the hosted Tail (private beta); sync is best-effort and never blocks or crashes your app.

Read the trust model in the spec before relying on local trails as evidence: self-signed trails are tamper-evident; hosted anchoring (v0.2) makes them stronger.

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

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

looptail-0.2.2.tar.gz (27.8 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

looptail-0.2.2-py3-none-any.whl (27.5 kB view details)

Uploaded Python 3

File details

Details for the file looptail-0.2.2.tar.gz.

File metadata

  • Download URL: looptail-0.2.2.tar.gz
  • Upload date:
  • Size: 27.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.10.15

File hashes

Hashes for looptail-0.2.2.tar.gz
Algorithm Hash digest
SHA256 e0ba2b25f2a54625c3c24b0b62af22f43e938eac437805b74781844994774622
MD5 fae83f1c641c33803df488a198aef779
BLAKE2b-256 3fa4f3625f65aa3a3e1653760acbc98fb9cb5b0adb909cd413600bbec0d00265

See more details on using hashes here.

File details

Details for the file looptail-0.2.2-py3-none-any.whl.

File metadata

  • Download URL: looptail-0.2.2-py3-none-any.whl
  • Upload date:
  • Size: 27.5 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.10.15

File hashes

Hashes for looptail-0.2.2-py3-none-any.whl
Algorithm Hash digest
SHA256 8ebef5a2a22b792ec1f0f7956504b212a2273f99997ccaca736748f0a0e7070b
MD5 1da89676dd860298f6564799ab4f13e9
BLAKE2b-256 326efffb8d5de2d9b46822906eb25fd2de143ef65923e6021a1a75e206706b57

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page