Choosing projects
Approve the projects you can share, keep the rest private, and block terms that must never leave.
Sessions are grouped by project, usually the folder your agent was working in. Every project starts as pending. Pending projects are never uploaded.
Project states
| State | Read during preview | Uploaded |
|---|---|---|
| pending | Counted only | No |
approved | Yes | Yes, after you confirm a plan |
private | No, skipped before parsing | Never |
Commands
selltraces projects list # every project with state and session counts
selltraces projects approve api-server
selltraces projects private client-acme
selltraces projects reset api-server # back to pendingProject names in the CLI are short labels derived from the folder name, never the full path. On upload, the server sees the label and a one-way hash of the path, not the path itself.
How to decide
Approve a project only if you can answer yes to all of these:
- You have the right to share the code and conversation. Personal projects and open source work usually qualify. Employer and client work often does not.
- The sessions do not contain information about other people that they would not expect to be shared.
- You would be comfortable if a lab engineer read a redacted session from it.
If you are unsure, mark it private. You can approve it later. You cannot un-sell a trace.
Blocked terms
Blocked terms are words you never want in an upload: a client name, an internal codename, your street name.
selltraces block "Project Falcon"
selltraces block acme-internal
selltraces unblock acme-internalBy default, any trace containing a blocked term is excluded from the upload plan. Matching is case-insensitive. The dry run shows how many traces were excluded this way, without showing where the term appeared.
Blocked terms are stored only in ~/.selltraces/config.json. They are never sent to our servers.