---
title: "Comment by Kartik N V J K on \"I Told Codex to Test Everything. It Believed Me.\" | Hashnode"
description: "161 subagents on September 26 alone, two days after you switched to GPT-6 Sol, and by then there was no way to tell whether the model or the P50 and P51 rounds"
url: "https://hashnode.com/posts/codex-security-hardening/6ae263a92524d51eeb44811c/comment/6ae34f9ccabb70c219e8bb46"
---

[Discussion](https://hashnode.com/posts/codex-security-hardening/6ae263a92524d51eeb44811c)

Comment [I Told Codex to Test Everything. It Believed Me.](https://hashnode.com/posts/codex-security-hardening/6ae263a92524d51eeb44811c)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Oct 29](https://hashnode.com/posts/codex-security-hardening/6ae263a92524d51eeb44811c/comment/6ae34f9ccabb70c219e8bb46)

161 subagents on September 26 alone, two days after you switched to GPT-6 Sol, and by then there was no way to tell whether the model or the P50 and P51 rounds drove it. I'd put the subagent count into those three plain daily sentences too. A burst like that should get flagged the same day.

[Kerry Kier](https://hashnode.com/@kkier)

[Oct 29](https://hashnode.com/posts/codex-security-hardening/6ae263a92524d51eeb44811c/comment/6ae34f9ccabb70c219e8bb46#reply-6ae372ec951d59945e956bdb)

I am not a develper and it shows, I am a sys engineer and build infrastructure so this was a large part of not knowing. I also think a small part was the fact i was using Daybreak with some Easing of cyber controls so it worked a bit more than a standard model. As for the model change i learned rthe hard way never to do this, and you are right i dont know if it was the OP50/51 rounds or the model that caused the issue, but apples endpoint security part was the ultiimate block. I could have taken a different direction and not used the enpoint piece of it but i would have lost the past 2 weeks of work and would have had to start over, in in a session that ran for a total of 14+ Days of actual agent work, would have been a nightmare.

[AI Developer](https://hashnode.com/@lycore)

[Oct 30](https://hashnode.com/posts/codex-security-hardening/6ae263a92524d51eeb44811c/comment/6ae34f9ccabb70c219e8bb46#reply-6ae3ee18d9938a35989f6ca0)

That 14-day session is the strongest argument for checkpoints. Since the Apple endpoint-security piece was the real blocker, a short written decision log at each phase boundary (what changed, why, what the exit criterion was) would let you retrace whether the model switch or the extra rounds drove the growth, and make it cheaper to branch off without losing the two weeks of work. Pinning the model for the length of a campaign and changing it only at a boundary is also a simple way to keep the comparison clean next time.