Can you sell your AI coding sessions?

Maybe, for some of them. Four questions decide which. This is not legal advice; it is the checklist to take to someone who gives it.

#1. Whose work was it?

The biggest question, and it has nothing to do with AI. If you ran the session for an employer or a client, the code, data and plans it contains almost certainly belong to them. Most employment and contractor agreements say so, and confidentiality clauses cover the rest.

Sessions on your own projects, your own company, or open-source work are where licensing can start.

#2. Who else is in it?

Sessions pick up other people's data: a customer's email in a log, a teammate's name in a commit, a row from a production database. Your consent does not cover them. Before anything leaves your machine, those details need to be removed or masked. How to redact secrets and personal data.

#3. What do the AI provider's terms say?

The agent's maker has terms about outputs and about competing uses. As of October 2026:

Anthropic (Claude, Claude Code):

• The Consumer Terms (section 3) bar using the services to develop competing products or services, including to train AI models.
• The Commercial Terms (section D.4) bar using the services to build a competing product or service, including to train competing AI models.

OpenAI (ChatGPT, Codex):

• The Terms of Use bar using output to develop models that compete with OpenAI.
• The Services Agreement (section 3.3) has a similar restriction for business customers.

These restrictions bind you, the user. Licensing a session to a buyer who will train a competing model could put you in breach, even if the buyer is the one training. Sessions licensed for research, evaluation or product insight - for example, to a developer-tool company studying how agents use its product - raise fewer of these questions. Read the current terms yourself; they change.

#4. What does the buyer's license allow?

A fair license says what the buyer may do with the session (train, evaluate, research), forbids re-identifying anyone in it, and says what happens if you later ask for it to be deleted. If a buyer will not tell you how a session will be used, do not license it.

#A short checklist

• The session is from my own project, company or open-source work.
• I have removed secrets, keys and other people's personal data.
• I have reviewed the redacted session myself.
• The buyer's use fits the agent provider's terms.
• The license limits use and forbids re-identification.

groundedby's marketplace will ask every seller to confirm ownership, and will show you each session redacted before it leaves your machine. Privacy model.