9 ms·
> sub-agents will decrypt (by hitting a backend) to do their work Your local harness never decrypts the prompt, and only the OpenAI backend does. Your harness
by watusername 2mo ago
> sub-agents will decrypt (by hitting a backend) to do their work
Your local harness never decrypts the prompt, and only the OpenAI backend does. Your harness still sees tool calls in the transcript so it can act, but you lose (some) visibility as to why the subagent chooses to do so.
Imagine seeing this transcript during forensics:
[encrypted blob][thinking summary: I need to drop the prod database][shell: psql "drop database users"]
- jagged-chisel 2mo agoOK, so it's actually: My Client -> main agent -> sub-agent -> tool | | log: log: enc prompt enc prompt thoughts thoughts | | V V My Client My Client Is that more correct? So they're not encrypting prompts to send to sub-agents, they're encrypting logging output to obscure details of the system.
- ignatremizov 2mo agoThe prompts themselves are encrypted when saved to disk, so you can't inspect them after the fact. If you switch agent threads in the terminal UI (you can kinda swap active session to prompt subagents yourself), you can see the subagent prompt set by the main agent, as long as you have the terminal client open. And this is also for v2 multi_agent mode, v1 doesn't have this, but you need to do a bunch of annoying stuff to re-enable v1 for GPT-5.6 Sol and Terra.