fix(web): closed plan sidebar stays closed when returning to a thread

[t3dotgg]

Closing the plan sidebar, leaving the thread, and coming back reopened the plan sidebar. It shouldn't.

The "user dismissed the plan for this turn" marker lived in a ChatView ref that gets wiped on every thread change, so re-entering a thread forgot the dismissal and the auto-open effect kicked in again. The dismissal now lives in a small module-level per-thread map (planSidebarDismissal.ts) that survives navigation. It stays keyed by turn, so a new turn producing fresh plan steps still auto-opens the sidebar, and explicitly reopening or starting a plan implementation still clears the dismissal.

---

Change authored by Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code

---

Note

Low Risk
Localized right-panel UX state with no auth, data, or API changes; behavior is limited to when the plan sidebar auto-opens.

Overview
Fixes the plan sidebar reopening after you leave and return to a thread even though you had closed it.

Dismissal state moves out of a ChatView ref (which was cleared on every thread change) into planSidebarDismissal.ts, a small module-level map keyed by thread and turn. ChatView now calls dismissPlanSidebarForTurn, clearPlanSidebarDismissal, and isPlanSidebarDismissedForTurn with activeThreadKey / scopedThreadKey everywhere dismissal mattered—toggle/close, activating the plan surface, thread reset with “open on next thread”, auto-open when plan steps arrive, and optimistic open when implementing a plan.

Turn-scoped behavior is unchanged: a new turn can still auto-open the sidebar, and explicitly reopening the plan or starting implementation still clears the dismissal for that thread.

^{Reviewed by Cursor Bugbot for commit 9589e10. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix plan sidebar to stay closed when returning to a thread

• Replaces a component-level useRef with a new module planSidebarDismissal.ts that tracks dismissed turn keys per thread in a Map, persisting across component lifecycles and thread navigation.
• The auto-open effect in ChatView.tsx now checks this shared store before opening, so a dismissed sidebar stays closed when re-entering the same thread on the same turn.
• Dismissal is cleared when the plan surface is explicitly activated, when the user manually opens the sidebar, or when a new implementation begins, ensuring auto-open works correctly for future turns.

^{Macroscope summarized 9589e10.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 03e6613b-fe43-43b3-a8b9-2294d941ad22

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved 9589e10

Simple bug fix that moves plan sidebar dismissal state from a component ref to a module-level Map, allowing the dismissed state to persist when navigating between threads. Self-contained UI state change with no security or schema implications.

^{You can customize Macroscope's approvability policy. Learn more.}