Hacker News: ignatremizov

New comment by ignatremizov in "Codex starts encrypting sub-agent prompts"

ignatremizov — Tue, 14 Jul 2026 16:45:18 +0000

The 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.

New comment by ignatremizov in "Codex starts encrypting sub-agent prompts"

ignatremizov — Tue, 14 Jul 2026 16:41:35 +0000

it's the multi agent config - multi_agent_v2 btw is still marked "Under Development" and they've said not to open issues for it. Then they deployed globally Sol and Terra under v2 - forcefully, through the model catalogue json (meaning user configs are ignored). v2 encrypts messages, v1 does not. Thankfully, you can override the catalogue with your own copy and set Sol and Terra multi agent to v1 again.

New comment by ignatremizov in "Codex starts encrypting sub-agent prompts"

ignatremizov — Tue, 14 Jul 2026 16:32:36 +0000

Haha, wow, I didn't expect to get quoted on Hacker News. Hello!

I guess "helped make Skynet auditable" may become my most popular open-source contribution, so I'm putting it on my CV.

The thing is that the subagent prompts already pass through the client - they have to, since the TUI can switch between subagents while they work. The change is just to save a copy of the prompt on disk while keeping the encrypted delivery path if necessary for Responses API.

Personally, I use multi_agent_v1 anyways (doesn't have this issue), since v2 is unstable and is a token burner.

Hope they address it so I don't have to keep maintaining it in my fork