feat: add activity feed default expansion setting

[AJV20]

Summary

• Adds a Settings → Appearance checkbox to expand new Activity disclosures by default.
• Preserves manual per-turn collapse/expand state so an explicit user toggle still wins.
• Makes live “Waiting on model” activity rows explain what the agent is doing before and after tool calls.

Test plan

• node --check static/ui.js
• node --check static/panels.js
• node --check static/boot.js
• node --check static/i18n.js
• python3 -m pytest tests/test_live_activity_timeline.py -q
• git diff --check

[nesquena-hermes]

Thanks for the PR — I read the full diff against origin/master (git -C /tmp/wt-cron-3080 diff origin/master...HEAD) and traced the activity-group lifecycle in static/ui.js. The wiring through api/config.py, static/boot.js, static/panels.js, and the appearance form looks clean and consistent with the existing session_endless_scroll precedent right next to it. The new _activityWaitingDetail() copy in particular is a nice quality-of-life touch over the previous flat "No tool activity has been reported yet." string.

One real bug: the setting works at group creation, then finalizeThinkingCard() slams it shut at end-of-turn

The new opt-in in ensureActivityGroup (static/ui.js:5447-5448):

let collapsed=opts.collapsed!==false;
if(window._activityFeedExpandedDefault===true) collapsed=false;
const savedState=_readActivityDisclosureState(activityKey);
if(live && _liveActivityUserExpanded === true) collapsed=false;
else if(live && _liveActivityUserExpanded === false) collapsed=true;

correctly opens new groups, but finalizeThinkingCard() at static/ui.js:7850-7864 runs at the end of every turn and force-collapses unless the user has explicitly clicked to expand:

if(_liveActivityUserExpanded !== true){
  group.classList.add('tool-call-group-collapsed');
  const summary=group.querySelector('.tool-call-group-summary');
  if(summary) summary.setAttribute('aria-expanded','false');
}

For someone who turned the setting on, _liveActivityUserExpanded stays undefined (they never had to click — that's the whole point of the toggle), so the group expands while streaming and then snaps shut the moment the assistant's response finalizes. That's almost certainly not the intent, and it's the exact failure mode the _liveActivityUserExpanded mechanism was built to prevent (the #1298 comment block at ui.js:5381-5394 calls this out explicitly).

Suggested fix — relax the force-collapse to also honor the default-expanded setting:

const shouldKeepOpen = (_liveActivityUserExpanded === true)
  || (window._activityFeedExpandedDefault === true && _liveActivityUserExpanded !== false);
if(!shouldKeepOpen){
  group.classList.add('tool-call-group-collapsed');
  const summary=group.querySelector('.tool-call-group-summary');
  if(summary) summary.setAttribute('aria-expanded','false');
}

The _liveActivityUserExpanded !== false clause preserves the existing "user explicitly collapsed mid-turn" semantics: if they actively close it during streaming, finalize still respects that.

Smaller note: persisted disclosure state for settled turns

The new branch runs before _readActivityDisclosureState() at ui.js:5448-5454:

let collapsed=opts.collapsed!==false;
if(window._activityFeedExpandedDefault===true) collapsed=false;
const savedState=_readActivityDisclosureState(activityKey);
…
if(savedState==='open') collapsed=false;
else if(savedState==='closed') collapsed=true;

That ordering is correct (saved closed-state wins for settled assistant:${aIdx} groups the user has explicitly closed). Worth a one-line comment though, since "default expanded loses to explicit closed" is exactly the right behavior but isn't obvious from the diff alone — easy to mis-refactor later.

Test coverage

tests/test_activity_feed_default_expand_setting_is_wired checks the literal if(window._activityFeedExpandedDefault===true) collapsed=false; substring is present. That catches the wiring but not the finalize regression above — a stronger assertion would be a regex-style check that finalizeThinkingCard's collapse guard mentions _activityFeedExpandedDefault, e.g.:

assert "_activityFeedExpandedDefault" in UI_JS.split("function finalizeThinkingCard")[1].split("\nfunction ")[0]

so the test fails if someone touches finalizeThinkingCard without updating the guard.

Verification plan

1. Enable the new setting in appearance.
2. Send a message that triggers a thinking → tool → thinking → response sequence.
3. Confirm the Activity panel stays open after the response settles, not just during streaming.
4. Manually click to collapse during streaming → confirm finalize leaves it collapsed.

Without (1+2+3) you'll get the "looks fine while streaming, snaps shut on done" UX which is more annoying than not having the setting at all.

[AJV20]

Addressed in fa318778.

What changed:

• finalizeThinkingCard() now keeps the live Activity group open when activity_feed_expanded_default is enabled, unless the user explicitly collapsed it during the turn.
• Added a guard assertion so the default-expanded setting remains represented in the finalize path.
• Added a comment clarifying that saved settled-turn disclosure state still wins over the default-expanded preference.

Verification:

• node --check static/ui.js
• python3 -m pytest tests/test_live_activity_timeline.py -q
• python3 -m pytest tests/test_ui_tool_call_cleanup.py tests/test_issue1413_li_path_coverage.py -q
• git diff --check

[AJV20]

Follow-up CI fix in 8f9c0a78.

The full suite had a static contract test that still expects the explicit _liveActivityUserExpanded !== true collapse guard in finalizeThinkingCard(). I rewrote the new default-expanded exception into that existing guard shape instead of hiding it behind a derived variable.

Additional verification:

• node --check static/ui.js
• python3 -m pytest tests/test_live_activity_timeline.py tests/test_issue1298_cancel_and_activity.py::TestIssue1298ActivityGroupExpandPersistence::test_finalize_thinking_card_respects_user_expand tests/test_ui_tool_call_cleanup.py tests/test_issue1413_li_path_coverage.py -q
• git diff --check

[nesquena-hermes]

Triage: HOLD pending UX review — labels: hold, ux

Two pieces here:

1. Settings → Appearance toggle to expand Activity disclosures by default. Visible settings UI surface — needs the standard screenshot pass at 390/1280/1440/1920 plus a comparison of new-turn activity behavior with and without the toggle. Per-turn manual collapse/expand winning over the default is the right contract; want to see it in action.

2. Waiting-on-model subtext. Replacing "Waiting on model" with a step hint (prompt/context review, latest tool action) is a meaningful change to the always-visible streaming UI. We'd like to see screenshots of each subtext state including the "before any tool ran" pre-step case to confirm the copy reads cleanly.

When you can share evidence at the four viewports for both pieces, we'll take another look. The backend additions (i18n strings, config knob, settings validator) look fine in isolation.

[AJV20]

UX evidence pass for the Activity default-expanded setting.

I re-checked the branch after the finalize-guard follow-up and exercised the requested viewport matrix at 390, 1280, 1440, and 1920 px. For each viewport I compared three states:

• default off: new Activity disclosure stays collapsed (aria-expanded=false, body hidden)
• default on: new Activity disclosure opens automatically (aria-expanded=true, body visible)
• default on + manual collapse: explicit per-turn collapse still wins (aria-expanded=false, body hidden)

Observed state matrix:

• 390 px: off collapsed; on open; manual collapse closed
• 1280 px: off collapsed; on open; manual collapse closed
• 1440 px: off collapsed; on open; manual collapse closed
• 1920 px: off collapsed; on open; manual collapse closed

Additional verification:

node --check static/ui.js
python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_issue1298_cancel_and_activity.py::TestIssue1298ActivityGroupExpandPersistence -q -o addopts=
# 10 passed
git diff --check origin/master...HEAD

So the UX contract I see is: the setting only changes the initial state for newly-created Activity groups, while saved/manual per-turn disclosure state still overrides it. That matches the helper text in Settings → Appearance.

[AJV20]

Refreshed this branch against current origin/master to clear the merge-conflict blocker after the release batch.

Verification on the refreshed head:

• node --check static/ui.js static/boot.js static/panels.js
• python3 -m py_compile api/config.py
• pytest tests/test_live_activity_timeline.py tests/test_ui_tool_call_cleanup.py tests/test_issue1413_li_path_coverage.py -q (29 passed)
• git diff --check origin/master...HEAD

Current note: this remains on UX hold pending the requested review; I only resolved the base conflict and kept the existing Activity/default-expanded scope.

[AJV20]

Refreshed this branch against current master again to clear the new changelog conflict after the latest release batch.

Verification on head 601687af:

• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• python3.11 -m py_compile api/config.py
• python3.11 -m pytest tests/test_live_activity_timeline.py -q -o addopts=
• git diff --check

The UX-review hold still stands; this update only removes the merge-conflict blocker.

[AJV20]

Refreshed this branch against current master after release EC moved the base.

Verification on head d0fc4709:

• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• python3.11 -m py_compile api/config.py
• python3.11 -m pytest tests/test_live_activity_timeline.py -q -o addopts=
• git diff --check

The UX-review hold still stands; this update only removes the merge-conflict blocker.

[AJV20]

UX evidence follow-up for the Activity default-expanded setting.

I ran a fresh isolated browser pass on the current head and captured the requested viewport/state matrix at 390, 1280, 1440, and 1920 px. For each viewport I compared:

• default off: new live Activity disclosure remains collapsed (aria-expanded=false, body hidden)
• default on: new live Activity disclosure opens automatically (aria-expanded=true, body visible)
• default on + manual collapse: explicit user collapse still wins (aria-expanded=false, body hidden)
• default on + running tool: live summary updates from the generic pre-tool state to the concrete tool progress state

Observed DOM/accessibility matrix:

390 px:  off collapsed; on open; manual collapse closed; running tool open with summary "Activity: 1 tool Reading files"
1280 px: off collapsed; on open; manual collapse closed; running tool open with summary "Activity: 1 tool Reading files"
1440 px: off collapsed; on open; manual collapse closed; running tool open with summary "Activity: 1 tool Reading files"
1920 px: off collapsed; on open; manual collapse closed; running tool open with summary "Activity: 1 tool Reading files"

The pre-tool visible subtext remains: Reviewing the prompt and context, then choosing the next action or composing the response. After a running read_file card is present, the summary reports the concrete tool action (Reading files) instead of a generic waiting state.

Additional verification on the same head:

python3.11 -m py_compile api/config.py
node --check static/ui.js
node --check static/boot.js
node --check static/panels.js
python3.11 -m pytest tests/test_live_activity_timeline.py -q -o addopts=
# 5 passed

Conclusion: the setting behaves consistently across the requested viewport widths, and the user’s explicit per-turn collapse still takes precedence over the default-expanded preference.

[AJV20]

Refreshed this branch against current origin/master to resolve the CHANGELOG.md conflict from the latest release batch.

Verification on the refreshed head 2f0d8046:

• python3.11 -m py_compile api/routes.py api/streaming.py
• node --check static/boot.js
• node --check static/sessions.js
• node --check static/ui.js
• python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_ui_tool_call_cleanup.py -q (26 passed)
• git diff --check

No scope change beyond merging current master and preserving the PR's Unreleased changelog entry.

[AJV20]

Refreshed this branch against current origin/master to clear the release-batch CHANGELOG.md conflict. The existing head still preserves the default-expanded Activity behavior through finalizeThinkingCard() unless the user manually collapses the live group. Verification on refreshed head 2813a65a:

• python3.11 -m py_compile api/config.py
• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_issue1298_cancel_and_activity.py tests/test_ui_tool_call_cleanup.py -q -o addopts=
• python3.11 -m pytest tests/test_1003_appearance_autosave.py tests/test_1003_preferences_autosave.py tests/test_batch_fixes.py -q -o addopts=

Results: 36 passed, 1 warning and 42 passed, 1 warning.

[AJV20]

Refreshed this branch against current origin/master again to clear the release-batch CHANGELOG.md conflict.

Verification on refreshed head d03d4fef:

• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• node --check static/i18n.js
• python3.11 -m py_compile api/config.py
• python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_ui_tool_call_cleanup.py tests/test_issue1413_li_path_coverage.py -q -o addopts=
• git diff --check

The default-expanded Activity behavior and waiting-detail coverage are unchanged; this push only refreshes the PR onto the latest base.

[AJV20]

Refreshed this branch against current origin/master to clear the latest release-batch conflicts in CHANGELOG.md, static/ui.js, and the live-activity regression tests.

The merge keeps the Activity default-expanded behavior through finalizeThinkingCard() unless the user manually collapses the live group, while also preserving the newer stream-start / first-token / post-tool waiting states from master.

Verification on refreshed head 44dd039c:

• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• node --check static/i18n.js
• python3.11 -m py_compile api/config.py
• python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_ui_tool_call_cleanup.py tests/test_issue1413_li_path_coverage.py -q -o addopts= (30 passed, 1 warning)
• git diff --check

The existing UX-review hold remains unchanged; this update only removes the merge-conflict blocker.

[AJV20]

Refreshed this branch against current origin/master after the release batch and resolved the CHANGELOG.md conflict by keeping this PR's Unreleased activity-setting entries above the new release history.

Verification on head c28f5949:

• git diff --check
• python3 -m py_compile api/config.py
• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_issue1413_li_path_coverage.py tests/test_ui_tool_call_cleanup.py -q (30 passed)

I also re-checked the earlier end-of-turn expansion concern: finalizeThinkingCard() now preserves the default-expanded preference unless the user manually collapsed the live Activity group, and the focused static regression asserts that branch.

[AJV20]

Refreshed this branch against current origin/master to clear the latest release-batch conflict while preserving this PR's Unreleased Activity-setting entries above the new release history.

Verification on refreshed head 9680b08b:

• python3.11 -m py_compile api/config.py
• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_1003_appearance_autosave.py tests/test_ui_tool_call_cleanup.py tests/test_issue1413_li_path_coverage.py
• git diff --check

The maintainer UX hold still needs the requested screenshot/evidence pass; this refresh only removes the merge-conflict blocker.

[AJV20]

UX evidence follow-up for the Activity disclosure setting and live status copy.

I ran a fresh isolated browser pass on the current head and checked the requested viewport matrix at 390, 1280, 1440, and 1920 px. The pass opened Settings → Appearance, verified the new toggle is present/visible, then compared new-turn Activity behavior with the default off, default on, a manual collapse override, and live running/post-tool states.

Observed DOM/accessibility matrix:

• 390 px: settings toggle visible; default off → aria-expanded=false, collapsed class present, body hidden; default on → aria-expanded=true, collapsed class absent, body visible; default on + manual collapse → aria-expanded=false, body hidden; live tool states showed Waiting on tool result with Searching workspace: search_files. Results will appear here. and post-tool Waiting on model with Last step: Searching workspace (search_files); now choosing the next action or composing a response.
• 1280 px: same results as 390 px.
• 1440 px: same results as 390 px.
• 1920 px: same results as 390 px.

The pre-tool state remained visible as Waiting for first model token with Stream connected; no model output has arrived yet. when Activity was expanded, and stayed hidden from the body when the disclosure was collapsed.

Additional verification on the same head:

python3.11 -m py_compile api/config.py
node --check static/ui.js
node --check static/boot.js
node --check static/panels.js
python3.11 -m pytest tests/test_live_activity_timeline.py -q
# 6 passed, 1 warning
git diff --check

Conclusion: the expanded-by-default preference is visible in Appearance across the requested widths, applies only as the initial new-turn disclosure state, preserves manual per-turn collapse, and the live status subtext remains concrete across pre-tool, running-tool, and post-tool waiting states.

[AJV20]

Refreshed this branch against current origin/master after the latest release batch; head is now cbd3bc64.

Conflict resolution was limited to CHANGELOG.md: kept this PR's ## [Unreleased] Activity-setting entries above the new release history.

Verification on refreshed head:

• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• node --check static/i18n.js
• python3.11 -m py_compile api/config.py
• python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_1003_appearance_autosave.py tests/test_ui_tool_call_cleanup.py tests/test_issue1413_li_path_coverage.py -q -o addopts= (36 passed, 1 warning)
• git diff --check

[AJV20]

Refreshed this branch against current origin/master after the latest release batch; head is now e844f620. Conflict resolution was limited to CHANGELOG.md: kept this PR's ## [Unreleased] Activity-setting entries above the new release history.

Verification on refreshed head:

• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• node --check static/i18n.js
• python3.11 -m py_compile api/config.py
• python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_1003_appearance_autosave.py tests/test_issue1413_li_path_coverage.py tests/test_ui_tool_call_cleanup.py -q -o addopts= (36 passed, 1 warning)
• git diff --check

[AJV20]

Refreshed this branch against current origin/master after the latest release batch; head is now 17e1adc7.

Conflict resolution was limited to CHANGELOG.md: kept this PR's ## [Unreleased] Activity-setting entries above the new release history.

Verification on refreshed head:

• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• node --check static/i18n.js
• python3.11 -m py_compile api/config.py
• python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_1003_appearance_autosave.py tests/test_ui_tool_call_cleanup.py tests/test_issue1413_li_path_coverage.py -q -o addopts= (36 passed, 1 warning)
• git diff --check

The UX hold remains; this only clears the merge-conflict blocker.

[AJV20]

Refreshed this branch against current origin/master after the latest release batch; head is now 22153594.

Conflict resolution was limited to CHANGELOG.md: kept this PR's ## [Unreleased] Activity-setting entries above the new release history.

Verification on refreshed head:

• git diff --check
• python3.11 -m py_compile api/config.py
• node --check static/boot.js
• node --check static/panels.js
• node --check static/ui.js
• node --check static/i18n.js
• python3.11 -m pytest tests/test_live_activity_timeline.py -q -o addopts= → 6 passed

[AJV20]

Refreshed this branch against current origin/master after the latest release batch; head is now e0d787a9.

Conflict resolution was limited to CHANGELOG.md: kept this PR's Activity-setting ## [Unreleased] entries above the current release history.

Verification on refreshed head:

• git diff --check
• python3.11 -m py_compile api/config.py
• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• node --check static/i18n.js
• python3.11 -m pytest tests/test_live_activity_timeline.py tests/test_issue1298_cancel_and_activity.py tests/test_ui_tool_call_cleanup.py -q -o addopts= → 37 passed, 1 warning

[AJV20]

Refreshed this branch against current master to clear the changelog conflict after the latest release batch.

Head: 994598be

Verification:

• python3 -m py_compile api/config.py api/streaming.py
• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• node --check static/i18n.js
• python3 -m pytest tests/test_live_activity_timeline.py tests/test_issue1413_li_path_coverage.py tests/test_ui_tool_call_cleanup.py -q -o addopts= → 30 passed
• git diff --check
• Isolated rerun for the transient CI failure: python3 -m pytest tests/test_tls_support.py::TestTLSEndToEnd::test_http_without_tls_still_works -q -o addopts= → 1 passed

The failed-job rerun API requires admin rights, so I amended/re-pushed the same merge resolution to retrigger checks.

[AJV20]

Refreshed this branch against current master to clear the changelog conflict after the latest release batch. The conflict resolution preserved this PR's Activity-setting ## [Unreleased] entries and kept the new upstream browser-smoke entry above the release history.

Head: b97be0c1

Verification:

• python3 -m py_compile api/config.py api/streaming.py
• node --check static/ui.js
• node --check static/boot.js
• node --check static/panels.js
• node --check static/i18n.js
• python3 -m pytest tests/test_live_activity_timeline.py tests/test_issue1413_li_path_coverage.py tests/test_ui_tool_call_cleanup.py -q -o addopts= → 30 passed, 1 warning
• git diff --check

[nesquena-hermes]

Shipped in v0.51.226 ✅ — cherry-picked (squashed net diff) onto release stage-p9, screenshot-approved. The 'Expand activity feed by default' Settings → Appearance checkbox is live. Thanks @AJV20! Closing as merged-via-release.