Your agent sessions are worth something: publish and sell them on a4sx
· Christoph Heuwieser
A long agent session holds more than its final diff. It holds the files the agent read, the commands it ran and what they returned, the approaches it tried and dropped, and the reasons it picked one path over another. Most of that is gone once you close the terminal. As of today, every signed-in account on a4sx with a verified email address can publish sessions and sell them, with no plan required. One thing to know up front: seller payouts are not active yet. Your earnings are recorded from your first sale; payouts start once they're switched on. This post covers why we think sessions are worth selling, how to tell whether one of yours is, and what it costs.
Why a session has value
The expensive part of agent work is rarely the final answer. It's the context that got you there: which config flag actually mattered, which error message was a red herring, which library version broke the build, which test only fails on CI. Building that context took hours of tool calls and tokens.
A buyer doesn't get a summary of your session. They get the session itself, and with Claude Code they can resume it: their agent picks up with everything yours already worked out, instead of re-deriving it from scratch.
Dead ends count too. A session that tried three approaches and ruled out two tells the next person which two to skip. A session that never reached a fix still shows where the fix isn't. We wrote more about that in why keep the dead ends.
This matters more as other things get cheaper. In Everything becomes anything I argued that code is losing its defensive value, while accumulated real-world work keeps it. A session is exactly that kind of work. Weights on your own disk made the point that good data, not base models, is the real bottleneck, and real sessions with real tool output are good data. And as Novel, recalled or borrowed? showed, a result without its trail is hard to check. The session is the trail.
When a session is worth selling
Good candidates usually have one thing in common: they solved a concrete problem that someone else will search for.
- A migration: a framework upgrade, a database move, a switch of build system. The steps carry over to other projects, and the gotchas are the valuable part.
- An integration: wiring up a payment provider, a sign-in flow, a cloud API with thin documentation.
- A debugging hunt: a flaky test, a memory leak, a race condition, especially one whose cause turned out to be somewhere unexpected.
- Well-documented dead ends: an approach that looked right and wasn't, with the evidence for why.
Some sessions aren't worth listing:
- Trivial ones: a rename, a one-line fix, a question a search engine answers.
- One-offs so tied to a single codebase that nobody else could reuse them.
- Anything with material you may not share: a client's code, an employer's internal details, data covered by an NDA. You are responsible for what you publish. Every listing goes through a mandatory scrub that removes token-shaped secrets such as API keys, and a listing where the scrubber still finds leftovers is blocked. But the scrubber looks for patterns. It can't know that a function name or a customer's domain is something you shouldn't share. Read your session before you list it.
How to publish and sell
- Save the session to your a4sx library, from Claude Code or Codex CLI.
- Open the Sell page and pick the sessions to sell. A listing is a collection: you publish a collection of your sessions as a listing, and buyers buy the listing. The scrub runs before anything is listed.
- Set a price: free, or from €5. Give it a title and a description that says which problem it solves.
- Publish. Buyers can see what a listing contains before they buy. After buying, they add it to their library and resume it.
Resume works in Claude Code today. Codex CLI sessions can be published and sold now as well; resume in Codex CLI is coming later.
You don't have to do the saving by hand. a4sx is built for agents first: point your agent at a4sx (connect your agent) and it can save sessions to your library over MCP. Listing a collection and setting its price happen on the Sell page, or through the REST API with your own signed-in session; your agent's MCP connection can't list or price anything.
A few guardrails come with opening this up. A seller on a free account can have up to 10 active listings. A seller's first listings go live right away and are reviewed after they are live. Anyone can report a listing, and listings that break the rules are taken down.
What it costs
- Publishing and selling are free for every signed-in account with a verified email address.
- On each sale, the platform fee is 30 % of the net price, which is the price excluding VAT. Stripe's payment fees are included in it. At 19 % VAT, a €10.00 sale is €8.40 net: the fee is €2.52, and your share of €5.88 is recorded as your earnings.
- A workspace plan lowers the fee. The current rate is on the Sell page.
- Payouts are not active yet. Your earnings are recorded from your first sale; payouts start once they're switched on. Until then, no money is transferred to sellers.
- Before any payout, Stripe verifies your identity.
- Selling is open to sellers established in the EU/EEA.
We won't tell you what you'll earn. Some sessions will sell and many won't, and the price is yours to set. What we can say is that a session sitting in an old terminal tab earns nothing and helps nobody.
Where to start
Look back over your last few weeks of sessions. Pick the one where you, or your agent, fought hardest for the answer, or the one that proved an approach doesn't work. That's probably the one someone else needs next. Here is how selling works.