3 pointsby smashah7 hours ago1 comment
  • smashah6 hours ago
    Hi all, with the recent Grok discourse with them hijacking basically all your code, I wanted to create something to give everyone access to an easy way to collect their own AI coding session traces so that you (if you want, you don't have to) can sell them later in a way where it remains secure and within your control at all times.

    Every AI lab subsidizes access to their models partly to get their hands on your sessions. In this AI goldrush, models are the shovels and our traces are the wood the shovel-makers build them from. So if our working sessions are that valuable, why are we giving them away for a mere discount to only one model provider at a time? I wanted to answer the question: what if we could sell our own traces to model providers directly in a way where the data is never at risk? That's why I'm building traice.market (WIP) and Traicer. Traicer is the open source collection service that runs on your machine, and you route selected Claude Code / Codex / OpenCode calls through and it saves to your own S3 compatible bucket (thanks alchemy.run and varlock for making integrating this feature securely very simple!)

    Each supported call gets credential-stripped, redacted (keys, JWTs, DB URLs, emails), encrypted with AES-256-GCM, and written to an S3 bucket you own. Keys never leave your machine. When traice.market is ready, it will let you sell traces without us ever being able to touch or read them: the marketplace only sees signed content-free metadata (provider, model, token counts, hashes), and a sale requires your explicit approval, with delivery re-encrypted on your machine to the buyer's key.

    I would love any feedback/questions etc.

    thanks!