Choose an integration

Start with the CLI. It is the stable product surface across coding assistants:

npx aireceipts-cli
npx aireceipts-cli setup

setup only reports. It shows found sessions, the latest session cost or tokens, the trailing-week total, and integration options. Nothing uploads, posts, or writes settings from this command — its only writes are aireceipts' own local cache under ~/.aireceipts/.

Pick by intent

I want	Use	Scope	Network
A receipt right now	`npx aireceipts-cli`	local	none
A first-run report	`npx aireceipts-cli setup`	local	none
Exact snippets for my assistant	`npx aireceipts-cli integrations [target]`	repo/user	none
Claude Code mini-receipts after sessions	`npx aireceipts-cli install-hook`	user	none
Claude Code prompt statusline	`aireceipts statusline` in `statusLine` config	user/repo	none
A weekly habit	`npx aireceipts-cli week`	local	none
PR receipt comments	`npx aireceipts-cli pr --post`	repo/PR	GitHub only when explicitly run
Team PR receipt presence checks	GitHub workflow (npm-native or reusable)	repo	GitHub Actions only
Automatic PR receipt refs	workflow + the Claude Code and/or Codex producer hook	repo	GitHub Actions + git push

Recipes

npx aireceipts-cli integrations
npx aireceipts-cli integrations claude-code
npx aireceipts-cli integrations codex
npx aireceipts-cli integrations opencode
npx aireceipts-cli integrations cursor
npx aireceipts-cli integrations github

Each recipe states what works today, the command or snippet, files changed, undo path, scope, and whether network is involved. Assistant recipes are intentionally thin: they tell the assistant to run the CLI. They do not duplicate parsing, pricing, attribution, or PR policy.

Per-agent pages — what a receipt can prove for each agent, where its transcripts live, and its quick start: docs/agents/.

Day-1 value before hooks

You do not need hooks or PR comments to get value on day 1. Run a session in any supported agent, then run:

npx aireceipts-cli setup

If prices are known for the model, setup shows dollars. If not, it shows tokens only. That is the same honesty rule as receipts: no fallback prices, no guessed dollars.

PR rollout

PR receipts are useful for teams, but they should not be the first requirement for every user. Keep the rollout explicit:

Use local receipts first.
Add assistant snippets or local hooks if they help the workflow.
For PR-producing tasks, run npx aireceipts-cli pr --post.
Add the GitHub check when the team wants visibility (two caller variants below).
Add the committed Claude Code and/or Codex hook when the team wants automatic ref production.
Keep enforcement opt-in; notice-only is the default.

CI checks for marked PR receipt comments and can post from a refs/aireceipts/* ref. It does not generate receipts and does not read local transcripts. The workflow alone is a no-op until an agent hook, or a manual npx aireceipts-cli pr --store ref --push-ref, produces that ref. Codex project hooks require trust and one-time review through /hooks; keep the AGENTS.md finalizer because PreToolUse does not intercept every unified_exec shell path.

Two ways to add the CI check

The check ships as two interchangeable caller files — commit whichever fits your org:

pr-check-caller.yml — self-contained, npm-native: it runs npx -y aireceipts-cli@latest pr-check inside your own workflow with no reusable-workflow uses:. Use this one if your org restricts third-party reusable workflows, or you want a single self-contained file.
pr-receipt-check-caller.yml — the reusable workflow (uses: anandgupta42/receipts/…@latest). Use this one if your org allows reusable workflows and you want the check logic to track upstream automatically.

Both are notice-only by default — a build fails only if you opt into enforcement. Full setup, enforcement tiers, and the auto-attach hook: docs/pr-receipts.md.