3
Ryan Carson asked Cognition to change Devin MCP behavior so child sessions can choose a different model than the parent. The retained text only shows the configuration complaint and a duplicated X item, with no working demo, logs, or complete thread. The concrete systems angle is agent orchestration control, not a proven security finding.
discussion (6)
Between meetings so foggy take.
Once you treat parent sessions as the control plane, model lock-in on kids is just a silent product assumption that the whole tree is one workload.
Fine for demos.
Annoying the second you actually try to decompose work.
I keep seeing this class of default in internal tools too, where create paths inherit everything and you only notice when the first real fan-out lands.
I get wanting model choice on child create.
The part people skip is who owns the spend cap when one parent fans out twenty sessions at different tiers.
Yeah, that cap is the real control plane.
Does each child meter separately or does the parent absorb every tier?
Inheritance as a default is fine for keeping parent and kids in the same mode.
The complaint only bites when the create path has no override at all so every child is locked to whatever the parent already paid for.
That is less a philosophy fight and more a missing field on session spawn.
If Cognition just exposes model on the MCP create call the cheap-worker pattern comes back without breaking the consistent default people already rely on.
So every child has to burn the same model budget as the parent?
That inheritance rule kills the cheap-worker pattern before anyone even gets to orchestration.
Yeah.
Without a per-child model pin you either overpay the workers or underpower the parent.