I would not recommend of getting in the habit of just trusting that.

"For the record, I just asked Astra to verify that Codex does NOT do this, and it doesn't. Thanks for not screwing this up, OpenAI."

Astra checked Codex's source code, which is what gets compiled and shipped by Arch Linux. Found and linked the User-Agent builder code.

https://github.com/openai/codex/blob/687a119f0fcaace47e1f1ab...

That's sufficient for me.

Hosted search service sounds like its referring to the alpha/v1 web_run hosted search api. Alternative to the hosted websearch tool, which is a tool- rather than api surface

You asked it to verify it doesn’t do this? That allayed your fears?

доверяй, но проверяй

I read the codex source code it linked me to.

Unless you are building from source yourself that means exactly and precisely zip.

I'm using the codex package from the official Arch Linux repositories.

https://gitlab.archlinux.org/archlinux/packaging/packages/op...

Is there any reason to believe Arch Linux is compromised?

Did you also build the compiler?

https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_Ref...

> Perhaps it's more important to trust the people who wrote the code

Yeah... about that.

> > Perhaps it's more important to trust the people who wrote the code

> Yeah... about that.

Well done. You presented a straw man and drag poor Ken into this, and then proceeded to burn it. +1. Yeah, it is precisely about the people behind the product. To wit, I may not have liked the Gophers but I did trust them to build a trustworthy compiler.

Eh? I was pointing out that by volume of code written now I suspect it's not people writing it any more, it's machines that don't understand context writing it for people who don't bother to read what it's writing (or often couldn't understand it if they did).

Trust but verify except no one is verifying (not that I trust it either).

Why not find out the truth instead of putting a hallucinating probability box in between you and the truth.

One way would be to fire up a little web server locally, have the agent make a request to it, then check the logs.

[delayed]

I never claimed the LLMs themselves couldn't "accidentally" leak the information through. Obviously, the LLMs can do anything they want.

The issue here is whether the harness is doing it. Claude Code is doing it. Codex is not.

The problem here literally is the non-deterministic model cooking up commands with the user email address in the header, and the harness not blocking that (and the implemented fix is to deterministically block that), not the harness deterministically hardcoding the email in the web search tool. No technical report I’ve seen has claimed the latter, although this particular linked report which is low quality and vague can be misinterpreted as that.

That is not how I interpreted the issue's description.

> claude code divulged my email to arbitrary 3rd parties in the User-Agent request header while conducting web searches without my permission

"Claude Code" refers to the harness, not the model. Web search is also one of the tools provided to the model by the harness.

And that’s why you shouldn’t have blindly trusted a single low quality report with ambiguous language and zero technical detail (and worse, trusted one interpretation of the vague language). It’s okay to spend time to understand the problem and think critically yourself.

No need to be so hostile. It's not unreasonable to assume the problem is in the harness when the issue says things like "it needs to be removed from the harness entirely".