Portable receipts
Strict JSON and readable Markdown keep the recovery record useful outside the extension.
Open source
The core is licensed Apache-2.0 so the snapshot, risk rules, receipt format, integrity checks, and close sequencing can be inspected and extended.
apps/extension browser surface
apps/web product + docs
packages/core schemas + lifecycle
packages/privacy deterministic guardrails
packages/receipts verify + export + diff
packages/extraction on-demand page textWhy open
A product with permission to close tabs should not hide the rules that decide what is safe, what is stored, or when the destructive action begins.
Strict JSON and readable Markdown keep the recovery record useful outside the extension.
Model suggestions cannot override the rule that unknown and risky state stays open.
Hashing, artifact validation, lifecycle state, and receipt diffs can be tested without a hosted service.
The repository includes a local 43-page synthetic laptop-research fixture. It avoids third-party pages and encodes an expected plan: 39 close candidates, four keep-open tabs, cited facts, and unresolved questions. Those numbers are fixture expectations, not customer results.
pnpm install
pnpm demo:generate
pnpm demo:serveChanges that increase closure power need stronger evidence than changes that preserve or keep state. Safety regressions are product regressions.
Commercial split
The intended business model charges for managed deployment, long-term hosted services, team policy, and support—not for the ability to export or restore your own receipt.
Schemas, risk rules, receipt verification, export, diffing, and local operation.
Optional hosted history, team controls, deployment support, and enterprise provider routing.
Receipt export, verification, and restore guidance remain part of the open contract.
Receipt first. Close second.
The quickstart and security pages are the shortest path to understanding what Tab Checkout can—and cannot—safely promise.