Select and submit traces
Scope the candidate set
Section titled “Scope the candidate set”Use the narrowest selector that describes your intent.
# Sessions from the last daytrace-commons-contributor submit --since 1d
# Sessions whose real working directory is this project or a descendanttrace-commons-contributor submit --project .
# Only locally discovered Codex sessionstrace-commons-contributor submit --source codex --since 7d
# Explicit Letta Trajectory v1 file or directorytrace-commons-contributor submit \ --source trajectory \ --trajectory ./trajectory-outputTrajectory files are never discovered implicitly. A missing --trajectory path is an error, not an empty batch.
Inspect without uploading
Section titled “Inspect without uploading”--dry-run runs parsing, redaction, the privacy canary, and envelope sizing without making the upload request.
trace-commons-contributor submit \ --project . \ --no-reasoning \ --dry-runProduce a submission manifest
Section titled “Produce a submission manifest”A project integration can retain the successfully submitted IDs:
trace-commons-contributor submit \ --project . \ --manifest trace-commons-ids.jsonThe manifest includes successful and already-submitted receipts. Refused and failed sessions are excluded. A manifest cannot be combined with --dry-run, because dry-run identifiers do not exist server-side.
Keep the manifest or local receipts: the stable IDs are how you track what happens after submission, remediate quarantine, and withdraw later.
Handle quarantined sessions
Section titled “Handle quarantined sessions”After addressing the reason a session was quarantined, re-run the bounded remediation path:
trace-commons-contributor submit --remediate-quarantinedRemediation preserves the stable submission_id so the corrected envelope can supersede the earlier stored version.
Local state and logout
Section titled “Local state and logout”The client keeps configuration, the device key, and hash-only receipts in its platform configuration directory. Override that directory with --config-dir or TRACE_COMMONS_CONTRIBUTOR_DIR when isolating environments.
trace-commons-contributor logoutLogout deletes the local contributor configuration, device key, receipts, and orphaned temporary files. It is not a substitute for withdrawing already submitted traces. See Daemon and withdrawal.