Skip to content

feat(settings): add maxNestingDepth and autoFlattenOnLimit settings round-trip - #21

Open
easonLiangWorldedtech wants to merge 2 commits into
mainfrom
up-2
Open

feat(settings): add maxNestingDepth and autoFlattenOnLimit settings round-trip#21
easonLiangWorldedtech wants to merge 2 commits into
mainfrom
up-2

Conversation

@easonLiangWorldedtech

Copy link
Copy Markdown
Owner

Part 2/8 of the task-tree series (builds on part 1).

Description

Adds two global settings that control subtask delegation:

  • maxNestingDepth (default 2, range 0-5): how many levels a subtask may nest. A value of 0 disables delegation entirely — every new_task runs inline.
  • autoFlattenOnLimit (default true): when the limit is reached, flatten the subtask into the current conversation instead of opening a new tab; when disabled such requests are rejected so you can continue directly.

Full round trip: global-settings schema + shared defaults, ExtensionState, SettingsView control bound to cachedState with save payload, webviewMessageHandler persistence through ContextProxy, ClineProvider getState/getStateToPostToWebview, runtime consumers using the shared defaults. Also completes the taskTree translation keys in all 17 non-English locales so check-translations passes standalone.

Test Procedure

  • pnpm --dir src exec vitest run core/webview/__tests__/ClineProvider.spec.ts (settings round-trip cases: true/false/unset)
  • pnpm --dir webview-ui exec vitest run src/components/settings/__tests__/ContextManagementSettings.spec.tsx (UI binding/save)

Pre-Submission Checklist

  • Scope: settings round trip only
  • Self-review performed
  • Tests added for new behavior (round-trip + UI binding, true/false/unset cases)
  • Visual snapshot: not applicable (settings control follows existing pattern)
  • Documentation impact: none required

easonliang28 and others added 2 commits August 17, 2026 10:32
Part 1/8 of the task-tree series (upstream-ready recomposition).

Adds `depth` to HistoryItem and a cycle-safe `backfillTaskDepth()` that
propagates parent depth through the delegation tree, so every task knows its
nesting level. Depth is surfaced for later use by settings validation,
environment details, and history-tree display.

Includes the single-open-invariant spec mock for backfillTaskDepth (folded in
from the series' CI fix) so this PR passes unit tests standalone.

Depth contract hardening:
- Children inherit their live parent's depth authority instead of assuming it,
  so a legacy non-authoritative parent never stamps its placeholder depth onto
  the child as a persisted fact (regression test added).
- computeTaskDepth now processes an ancestor reached after exactly
  MAX_DEPTH_WALK hops; only strictly longer chains are rejected (boundary
  regression test added).
…ound-trip

Part 2/8 of the task-tree series (upstream-ready recomposition).

Adds two global settings that control subtask delegation:

- `maxNestingDepth` (default 2, range 0-5): how many levels a subtask may
  nest. A value of 0 disables delegation entirely — every new_task runs inline.
- `autoFlattenOnLimit` (default true): when the limit is reached, flatten the
  subtask into the current conversation instead of opening a new tab; when
  disabled such requests are rejected so you can continue directly.

Full round trip: global-settings schema + defaults, ExtensionState,
SettingsView control bound to cachedState with save payload, webviewMessageHandler
persistence through ContextProxy, ClineProvider getState/getStateToPostToWebview,
runtime consumers using the shared defaults. Includes focused tests for UI
binding/save, persistence, and the saved value returned to the webview.

Also completes the taskTree translation keys in all 17 non-English locales so
check-translations passes standalone (folded in from the series' CI fix).
@easonLiangWorldedtech
easonLiangWorldedtech marked this pull request as ready for review August 17, 2026 02:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants