Describe the bug
rubber-duck reviews sometimes use the same model family as the primary session instead of selecting an independent reviewer, reducing the value of adversarial review.
i have observed this on a variety of models. most recently using 5.6 Terra - Max
Affected version
v1.0.78
Steps to reproduce the behavior
Have code/plan/contract whilst working in a gpt-5.6-terra session and request a rubber-duck review...
you then see this: Rubber-duck(gpt-5.6-terra) Assess audit design quality
└ Agent started in background with agent_id: audit-design-duck. You'll be notif...
Expected behavior
I would expect a different model family selected from the current model being used in the session.
Additional context
No response
Describe the bug
rubber-duck reviews sometimes use the same model family as the primary session instead of selecting an independent reviewer, reducing the value of adversarial review.
i have observed this on a variety of models. most recently using 5.6 Terra - Max
Affected version
v1.0.78
Steps to reproduce the behavior
Have code/plan/contract whilst working in a gpt-5.6-terra session and request a rubber-duck review...
you then see this: Rubber-duck(gpt-5.6-terra) Assess audit design quality
└ Agent started in background with agent_id: audit-design-duck. You'll be notif...
Expected behavior
I would expect a different model family selected from the current model being used in the session.
Additional context
No response