[theturtletalks]

They mentioned a few things

1. Sessions are locked into Codex and Claude Code so you can’t take a session with you. Pi solves that since they all stay Pi sessions and you can change models in the same session

2. Subagent prompts are not shown. Pi solves this by not supporting subagents out of the box. You can use a number of subagent extensions or build your own which will not be encrypted or hidden.

3. Thinking is hidden and obfuscated. Pi can’t solve this since this is server-side. Though the Codex app is closed source and they could hide more things in that harness. Pi shows you as much as it can from the API. You can also run another model to “decipher” the thinking which you can’t in Codex.

[rahimnathwani]

I see your point. I was thinking mainly about #3 and how nothing, not even pi, can solve that when the reasoning traces are encrypted by the model provider.

[theturtletalks]

I’ve heard of people using DeepSeek to reverse engineer those thinking tokens. Even though they don’t tell you the thinking content, they do tell you how many tokens were used. You can ask DeepSeek how we got from A + x thinking tokens = B.

Claude and Codex flag this as a distillation attempt so you have to use an open weight model and the results are, of course, just a guess.

[apitman]

I'm sure you were referring to the desktop app but codex CLI is open source