UI bug: 'Bypass permissions' status persists visually after session reset but doesn't actually apply

Bug Description

The \"Bypass permissions\" mode indicator in the UI shows the previous session's setting even after starting a new session where the default (non-bypass) mode should apply.

Steps to Reproduce

1. In a project session, manually select \"Bypass permissions\" from the permissions dropdown in the UI
2. Use /clear or start a new Claude Code session for the same project
3. Observe that the UI still shows \"Bypass permissions\" as the active mode

Expected Behavior

If \"Bypass permissions\" was only a session-level selection (not persisted to settings.local.json), the new session should show the actual default permission mode — and the UI indicator should reflect that.

Actual Behavior

The UI indicator still shows \"Bypass permissions\" even though the setting was not persisted. This creates a false sense of security/confusion: the user believes bypass is active, but tool invocations may still trigger confirmation dialogs.

Impact

Users are misled into thinking their permission preference is active across sessions when it is not. The mismatch between the displayed state and the effective state is confusing and constitutes a UI consistency bug.

Suggested Fix

• Either persist the session-level bypass selection automatically to settings.local.json
• Or reset the UI indicator to reflect the actual effective permission mode at session start

Environment

• Claude Code (claude.ai/claude-code)
• OS: Windows