[UX] Code tab sidebar: "More" single-item redundancy, missing section separators, no feedback path from Claude App

Bug 1 — "More" dropdown in Code tab contains exactly one item

Current behavior:
Clicking "More ˅" in the Code sidebar opens a popup with a single entry: Customize sidebar.

Problem:
A disclosure control that wraps one item provides no organizational value and costs the user an extra click.

Suggested fix:
Promote Customize sidebar directly into the sidebar list and remove the "More" wrapper, or keep "More" only when it contains ≥ 2 items.

---

Bug 2 — No visual separator between navigation items and session history (affects both Code and Cowork tabs)

Current behavior:
In both the Code and Cowork tabs, navigation items (e.g., Routines, Dispatch, Customize) and session/task history records are rendered in a single unseparated list. History items appear directly below navigation labels with identical spacing, making them visually indistinguishable from sub-items of the section above.

Problem:
The lack of any divider — section header, horizontal rule, or increased spacing — causes users to misread the hierarchy. Session records appear to be children of the navigation label immediately above them rather than a separate section.

Scope:
Reproducible in both the Code tab and the Cowork tab.

Suggested fix:
Add a visible separator (e.g., a label such as "Recent", or a horizontal rule) between the navigation group and the session history list, consistent across all tabs.

---

Bug 3 — No bug reporting path from Claude App; /feedback only exists in Claude Code CLI terminal

Current behavior:
There is no feedback or bug report mechanism inside Claude App (desktop), including the Code tab. The only way to run /feedback is to open a separate Terminal application and use Claude Code CLI from the command line.

Notable:
The Claude App's own Code tab does not support /feedback either. A user who encounters a bug anywhere in Claude App must open a separate Terminal application, launch Claude Code CLI, and run /feedback from there — despite the Code tab being the closest in-app surface to the CLI experience.

Problems:

• High friction: reporting a bug requires switching to an entirely separate application (Terminal).
• Context loss: /feedback captures the CLI session transcript only — it has no access to the Claude App session where the issue occurred. UI state, conversation history, and the steps that triggered the bug cannot be included.
• Discoverability: most non-technical users will never find /feedback in the CLI, effectively silencing their bug reports.

Suggested fix:
Add a "Report a problem" entry point accessible from all tabs in Claude App (Chat, Cowork, Code) that submits feedback without requiring the user to leave the app, and captures relevant context from the surface where the issue occurred.

---

Platform: macOS 15 / Claude App desktop
Reproducible: Yes, consistently across sessions