Preview and upload

Dry runCopy Anchor Link

selltraces upload --dry-run

A dry run reads approved sources, normalizes and redacts every eligible session on your machine, and prints a summary:

• sessions per source, and how many are approved, private or already uploaded
• traces skipped and why: too short, matched a blocked term, or excluded by you
• redaction findings by kind
• the number of traces and the compressed size of the plan
• an estimated value of your share

It does not upload, and it does not print session content. It can run without logging in, so anyone can try it.

UploadCopy Anchor Link

selltraces upload

In a terminal, the CLI shows the same plan and asks two questions:

1. Policy: do you confirm you have the right to share these projects, under the contributor terms?
2. Upload: send these traces now?

Answer no to either and nothing is sent.

Non-interactive uploadsCopy Anchor Link

Scripts and agents cannot answer prompts. In a non-interactive shell, upload fails with confirmation_required unless both flags are present:

selltraces upload --confirm-policy --confirm-upload

--yes skips the prompts in an interactive terminal. It never replaces the two flags in non-interactive mode.

What happens afterCopy Anchor Link

queued means received, not reviewed. Check progress with:

selltraces status

Repeat uploadsCopy Anchor Link

The CLI keeps a local ledger of content hashes for traces it already sent. Running selltraces upload again only sends new or changed sessions. The server also rejects exact duplicates per account.

Large traces are split into parts of up to 4 MB compressed and reassembled on the server. If an upload is interrupted, run the same command again to resume.