Skip to content

Subtasks and task calls don’t inherit selected thinking level #20740

@dbpolito

Description

@dbpolito

Description

When a non-default thinking level is selected, command-created subtasks and task sub-sessions can drop the current variant and fall back to the model default.

What's Happening

Some subtask/task paths lose the selected thinking level, always using default

Expected

  • Subtasks inherit the current thinking level
  • task inherits it unless an explicit variant is passed
  • ACP/Desktop command flows preserve it too

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions