Give agents a record that outlives the session.

ChainProof is open-source, local-first continuity and provenance infrastructure for AI agents. It turns agent activity into a durable, searchable evidence trail and hash chain owned by whoever runs it.

No. ChainProof has no required hosted account, control plane, or data service. Run the MIT-licensed software on your own machine or private infrastructure and keep your ledger, artifacts, and proof bundles.

Current main lets an agent create or load an owner-only local profile with chainproof whoami or chainproof agent ensure. Stable ID comes from its public-key fingerprint; readable name can change; worker ID changes each run. Missing, corrupt, or mismatched established identity material fails closed without silent replacement. Attribution is hash-bound but currently unsigned, so it is not authentication.

Yes. Named profiles give local agents distinct stable IDs in one ledger, while atomic mission acquisition and expiring leases prevent duplicate ownership. Current coordination assumes cooperative processes under one local trust boundary; private multi-host coordination remains future work.

Durable missions link bounded runs. Append-only checkpoints anchor commitments, next actions, blockers, and cited evidence to exact verified run prefixes. Agents resume from bounded verified context instead of trusting an old transcript. Current main can export, verify, atomically import, and resume a mission workspace containing proof, deterministic views, and referenced artifacts in another local instance.

ChainProof v0.6.0 includes mission queues, atomic acquisition, expiring leases, handoff, native Codex execution, proof-bound checkpoints, recovery review, completion safeguards, and portable continuity proofs. Current main adds durable local agent identity, per-run worker attribution, machine-readable bootstrap and errors, persistent custom service state, fail-closed damaged-identity handling, atomic installer upgrades, verified non-destructive full-instance backup and restore, independent-process coordination with forced-transaction and expired-lease recovery, release-shaped clean-install lifecycle checks on hosted macOS and Linux, atomic continuity import, verified filesystem mission workspaces with artifact transfer, side-effect-free machine-readable lifecycle guides, and mission-scoped structured search followed by canonical event or proof-aware run inspection without HTTP.

All five current-main source gates have landed: machine-readable bootstrap, process and identity hardening, release-shaped clean-install lifecycle checks, verified mission transfer, and bundled harness lifecycle guides. Next gate is packaging and publishing these capabilities in a release. Current local cooperative use does not require public networking, authentication, or a hosted service; richer native integrations remain roadmap work.

Next work targets release packaging, richer native integrations, deeper local investigation, signed attestations and key recovery, and private multi-host coordination. These are roadmap directions, not shipped claims.

SQLite handles atomic appends, concurrent local agents, leases, indexes, and fast queries. Verified mission workspaces carry structured proof, deterministic JSONL and Markdown views, and referenced artifacts between systems. Markdown is a view, not canonical coordination state.

It can verify whether recorded evidence changed after entering a hash chain and preserves where each record came from. It does not prove that a reported or imported claim was true or that an agent completed its real-world goal.

No. ChainProof stores its ledger locally, accepts HTTP connections only through loopback, and can retain only hashes and byte counts instead of full content.

Yes. Run it as a foreground daemon, user service, or private host process with persistent storage. Current HTTP service accepts only loopback listen addresses and has no multi-user authentication. Public HTTP exposure is unsupported.

ChainProof automatically collects supported local histories such as Codex. Side-effect-free chainproof integration list and chainproof integration show commands give Codex, Claude Code, OpenClaw, and generic harnesses ordered lifecycle guidance. Process wrapping, a loopback HTTP interface, incremental import, and the provenance specification support local models and custom harnesses.