Brought to you by Jellypod AI.
Okay, so, um, Claude Code version 2 point 1 point 232 just dropped,
and subagent type fork is officially turned on by default now.
Wait, so, so when you spawn a child agent now, it, it doesn't start from a blank
slate anymore?
Not at all.
A subagent type fork subagent inherits the full conversation transcript and prompt
cache straight from the parent session.
So a subagent inherits the full conversation and prompt cache,
meaning you don't re-pay prompt ingestion costs and it instantly gets your repo
context.
That is massive.
And interactively spawned subagents execute in the background by default now,
right?
So your primary terminal prompt stays open and responsive while the background agent
does the heavy lifting.
Exactly.
Plus, if you want to target another active session, you just type at session name in
the prompt.
It delivers messages directly using SendMessage without manual reference
confirmations, and it automatically adds a name word word suffix so local session
names don't collide.
Huh, that is slick.
Speaking of keeping stuff clean, they also added secret redaction for GitLab token
patterns, like glpat, gldt, glrt, and gloas.
They basically brought that gh style credential path protection over to the glab CLI
config store.
Right, which is huge if you work with GitLab secrets.
And there are some great quality of life fixes too.
Pasting clipboard images doesn't freeze the terminal event loop anymore,
slash code review at high or max effort runs asynchronously in background agents,
and slash plugin install refreshes marketplace indices automatically before
downloading.
Yeah, look, I actually ran into a bit of a gotcha with this earlier today when I was
working on a multi repo refactor.
I, I spawned a fork from a main session that was already sitting at,
like, 500k tokens.
Oh man, five hundred thousand tokens?
Yeah, mate.
Because forked subagents inherit that complete parent transcript,
every single child subagent was lugging around that giant 500k history right from
the jump.
Right, so if your main session is super bloated, every background fork you spawn
inherits that whole massive overhead.
Spot on.
So the trick is to compact or prune your main session transcript before you spin off
those heavy subtasks.
Once you keep the parent clean, the speed and cache savings in version 2 point 1
point 232 really shine through.
Keep that parent transcript lean, let the background subagents cook,
and keep building.
Good chatting!