What should Pin do in the “By project” view?

[Phoenix500526]

Hi @jackwener and @sunheyi6,

I'd like to confirm the intended behavior of Pin in the sidebar.

Current behavior

In the By project view, choosing Pin does not change the task's
position or show any visible pin indicator. The only visible change is that
the menu action becomes Unpin.

The state itself is saved correctly: after switching to By time, the same
task appears under Pinned as expected. This makes Pin look like a no-op
while the user remains in the project view.

History

• @jackwener introduced the user-facing Pin/Unpin action in
  3afda020,
  describing it as a way to "pin a chat to the top." A later change added the
  dedicated Pinned section at the top of the normal history view.
• @sunheyi6 introduced the folder-style project grouping in [codex] Improve project-grouped sidebar #557. That path
  groups tasks by project, but does not define how isFlagged should affect
  ordering or presentation inside a project.
• feat(desktop): let users pin conversations in the session list #3015 says pin state should survive grouping-mode changes, while feat(ui): discuss priority-based conversation ordering and activity filtering #1737 says
  project hierarchy should not be flattened. Neither appears to settle what a
  pinned task should look like while By project is active.

Question

Was the current behavior intentional, or was the interaction between Pin and
project grouping missed when the second view was added?

If it was missed, I see three possible directions:

1. Keep each task in its project, move pinned tasks to the top of that project,
   and show a small pin indicator.
2. Add a global Pinned section above the project groups.
3. Treat Pin as a By-time-only feature and hide the action, or explain its
   effect, while By project is active.

I currently lean toward the first option because it preserves project
hierarchy while still giving immediate visible feedback. Before proposing a
change, however, I'd like to confirm the original design intent.

Automation disclosure: OpenAI Codex drafted and submitted this discussion at
the account owner's request.