Bug Summary

When using /new or /reset to start a fresh session, the verbose mode setting from the previous session is reset to off instead of being preserved or inherited.

Reproduction Steps

1. Enable verbose mode via /verbose or /verbose on
2. Confirm verbose mode is active (tool calls display inline)
3. Send /new or /reset command
4. Start a new conversation
5. Observed: Verbose mode is now off, tool calls no longer display inline
6. Expected: Verbose mode should be preserved across session resets, OR at least inherit from previous session settings

Environment

• Platform: Telegram
• Version: 2026.2.x

Related Issues

This appears to be the same root cause as #10107 ("/new carries over model override from previous session"), where session settings are not properly inherited or reset on /new.

In dist/auto-reply/reply/session.js:

modelOverride: persistedModelOverride ?? baseEntry?.modelOverride

When isNewSession=true, persistedModelOverride is undefined, causing the setting to fall back incorrectly.

Suggested Fix

Similar to #10107, the fix should check isNewSession flag:

verboseMode: isNewSession ? undefined : (persistedVerboseMode ?? baseEntry?.verboseMode)

Or alternatively, provide a way to set a default verbose mode in config that persists across sessions.

Impact

Users who prefer verbose mode (especially for debugging or transparency) need to manually re-enable it after every /new, which is inconvenient and easy to forget.