Live data from Hacker News

Stealing Reasoning Traces from Proprietary LLM APIs

stolen-thoughts.com

251–260 of 325 posts

Re: Stealing Reasoning Traces from Proprietary LLM APIs

#251
post #138

"Stealing" something you already paid for (tokens), but that you can't have access to(!). And trained on the sum of human knowledge. Training on other model outputs ought to be business as usual, stop using morally charged terms made up by future monopolists: https://thomasdullien.github.io/posts/2026-06-15-rl-economic...

Suppose you hired a consulting firm to write a report, and they delivered the report but not the internal conversations they had when developing it. You exploit a vulnerability in their phone system to get those conversations. You can argue over semantics of whether “theft” is what you did, maybe the right word is “espionage” or “spying”, but that either way we probably agree you are guilty of something? Paying for t…

Except you paid for the words of the conversation..

Re: Stealing Reasoning Traces from Proprietary LLM APIs

#252

Earlier quoted context omitted.

I personally read the thinking traces to know if the model is on the right direction

I'm not saying they're not useful, of course they are. I am disputing that they are part of the agreed bargain between you and the proprietary LLM providers. They explicitly do not promise reasoning traces. You (general you) agree to those terms and pay for that bargain anyways.

We "agree" to many things that are deeply unfair.

Re: Stealing Reasoning Traces from Proprietary LLM APIs

#253

Earlier quoted context omitted.

Reread what he called a morally charged, made up term by future monopolists. Stealing. Not distilling, not stealing “non rivalrous goods.” Just stealing. Do you agree with what he actually said?

Yes, "tokens, trained on the sum of human knowledge", are the most absolutely, unambiguously clear example of a non-rivalrous good I've ever seen. The current copyright status quo has them placed in the public domain . There is literally nothing wrong with "stealing" those tokens. They have exactly zero legal protection. "Stealing" those AI output tokens is so fundamentally impossible that it wouldn't be "stealing" i…

There are bunch of legal protections. They may not fall under copyright, but depending, you could be looking at breach of contract, trade secret misappropriation, CFAA, and also, if you buy them off someone else, now we’re into tortious interference.

Re: Stealing Reasoning Traces from Proprietary LLM APIs

#254
post #252

Earlier quoted context omitted.

I'm not saying they're not useful, of course they are. I am disputing that they are part of the agreed bargain between you and the proprietary LLM providers. They explicitly do not promise reasoning traces. You (general you) agree to those terms and pay for that bargain anyways.

We "agree" to many things that are deeply unfair.

Yet we have the option to decide not to participate. That is an option.

Re: Stealing Reasoning Traces from Proprietary LLM APIs

#255
post #226
post #213

Earlier quoted context omitted.

The only "secret" there is a very basic instruction that the model receives, like "summarize current state and upcoming work" before compaction - same model that was just running your inference, with same cache, only server side, with no extra tools or capabilities. Then the fresh context gets the output from that as an encrypted blob + codex then injects up to 64k tokens of previous conversation, the latter part is…

The compaction prompt doesn't seem like the valuable thing here. I suspect they're protecting the compaction result itself. If you're trying to distill a model, collecting lots of examples on how a large conversation gets compacted to a smaller summary is particularly useful data.

No, you can give the model same prompt and it will give you a similar compaction result. On the backend, that's precisely what happens. There's nothing else going on in that encrypted blob, it's just summary of what model responds with when prompted "summarize current state and upcoming work".

Re: Stealing Reasoning Traces from Proprietary LLM APIs

#256

Earlier quoted context omitted.

Maybe but I try to give people the benefit of the doubt, especially when the argument at face value is factually incorrect.

This tired argument--that copyright infringement is not "stealing"--is at least as old as my Commodore 64.

Yeah, considering that taking trade secrets is absolutely stealing, this could be considered stealing

Re: Stealing Reasoning Traces from Proprietary LLM APIs

#257

You cannot steal what is not owned. At least in the EU there is no copyright for LLM outputs, so I guess all they might do is violate the terms of service.

they also can't claim to be the owner of the output either because they can't claim to have had a valid license for the inputs.

Actually, this is untrue

Re: Stealing Reasoning Traces from Proprietary LLM APIs

#258
post #74

If I'm reading this right, they literally just ask a LLM to tell them what the traces say, with the key being that the traces are portable across LLM models, so they can switch to a smaller one that's easier to jailbreak.

nothing scientific here, they basically just figured out some real issues caused by bad engineering practice.

Re: Stealing Reasoning Traces from Proprietary LLM APIs

#259

Apparently you can do the same by simply running it without reasoning, while giving it a thinking tool... >guys you do know you can just disable thinking, and instead give it a "deep_think" tool, and it will call it with internal CoT reasoning format right? >gl fixing that https://x.com/_can1357/status/2087228354399265125?s=20

I've been doing that since before reasoning was a thing baked into the models, it always performs better this way. Except for some providers/models where you just can't easily turn it off, now I just avoid them. This way I save tokens and have full control of the reasoning.

How does it save tokens?

Re: Stealing Reasoning Traces from Proprietary LLM APIs

#260

Earlier quoted context omitted.

> If they charge by the token, all your tokens are belong to you I’m not sure this argument is correct. You can sign whatever contract you like with the model provider, right? Including “you are entitled to the end product but not the intermediate scratch work”? Coming from a place of genuine curiosity: is there some precedent or statute that would invalidate that contract? I don’t see why the reasoning tokens belong…

Sure, but the current one is charged per token in & token out. Not per completion / task / hour / whatever. You can't charge per token and then say "you stole that token". Again, they can unilaterally decide not to sell you tokens anymore, at any time, for any (legal) reason. But as it stands right now, it can't be stealing.

Read the TOS. It can absolutely be stealing.

Are you a lawyer?

Post reply on HN