[BUG] /clear drops ultracode (model reverts to non-ultracode) while the corner effort indicator still shows ultracode

Bug

After running /clear, the agent loses awareness that the session is in ultracode and behaves as a non-ultracode session, even though the ultracode effort indicator in the bottom-right of the window still shows ultracode.

The corner indicator (effort-level state) and the standing ultracode system-reminder (the thing the model actually reads to know it should default to Workflow orchestration) are separate pieces of state. /clear resets/omits the system-reminder but leaves the indicator showing ultracode, so the UI and the model's actual behavior disagree.

Expected behavior

/clear should re-establish ultracode the same way starting a fresh session does: if the session/indicator is in ultracode, the standing ultracode system-reminder should be (re-)injected so the model continues to default to multi-agent/Workflow orchestration. The corner indicator and the model's actual mode should never disagree.

Actual behavior

• Before /clear: session is in ultracode; indicator shows ultracode; model orchestrates accordingly.
• Run /clear.
• After /clear: indicator still shows ultracode, but the model no longer treats the session as ultracode — it defaults to non-ultracode behavior. The only reliable way to re-engage it is to re-type the literal ultracode keyword in a prompt.

Steps to reproduce

1. Put the session in ultracode (indicator in the bottom-right shows ultracode).
2. Run /clear.
3. Send any substantive prompt.
4. Observed: indicator still says ultracode, but the model behaves as a non-ultracode session (no Workflow orchestration by default).

Environment

• Claude Code 2.1.169
• Windows 11, Windows Terminal (terminal CLI surface)

Related issues

This appears to be the /clear instance of an already-reported class of "effort indicator vs. actual state" desyncs:

• #64817 — ultracode: true in settings.json does not inject the session-start ultracode system-reminder. A comment there describes the same indicator-vs-state mismatch: the indicator comes up as ultracode but after the first prompt the harness reports "Ultracode is off"; only the literal keyword re-engages it.
• #37161 — /clear resets effortLevel to medium, ignoring settings.json (closed by the stale-bot, not actually fixed; filed for the VS Code extension and predates the ultracode keyword rename).
• #66266 — Effort/model selection ("ultracode") reverts to "extra" when switching chats.

The common thread: session-resetting actions (/clear, first prompt after a settings-driven start, switching chats) drop the ultracode system-reminder while leaving the effort indicator intact, so the visible indicator stops reflecting the model's actual mode.