[FEATURE] Cowork: persist a chat's open tasks in the Progress panel across sessions

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Problem

I use Cowork for a long-running project split across several chats, each with its own
open items. The Progress panel in the right sidebar is where I'd naturally check them:
I open a chat and in two seconds I see what's still pending.

Today that doesn't work. The panel only renders tasks that were touched in the current
exchange, so when I reopen a chat the next day it's empty, even though the tasks are
still open. To see them again I have to ask Claude to list them, and Claude has to
rewrite each task's subject — a status-only update renders as Task #15 with no text
at all. So the panel shows either nothing or placeholders.

Two smaller things make it worse:

• The description field is never displayed, so the title is the only place to put

information.

• Clicking a task does nothing — I expected it to jump to where that item was discussed.

What I'd expect

When I open a chat, the Progress panel shows that chat's open tasks, with their text,
without anyone having to re-emit them. They stay until they're completed or deleted.
Per-chat scoping is right and I don't want it changed — each chat having its own list is
the useful part.

Proposed Solution

Suggestions, in order of how much they'd help me

1. Render a chat's open tasks on load, from the stored task list, not only tasks touched

in the current exchange.

1. Render the current subject whenever a task is updated, including status-only updates,

instead of falling back to "Task #N".

1. Optional: show the description on expand, and make clicking a task scroll to the

message where it was created.

Context

Non-developer use case: I'm an architect using Cowork to run a brand/identity project
for a family business, not to write code. The app is genuinely useful — this is a
suggestion, not a complaint. Item 1 alone would solve it for me.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

I run a branding project for a family business in Cowork, split across five chats
(visual identity, Instagram content, web, print, marketing). Each chat has its own
open items.

1. On Tuesday I work in the "visual identity" chat. Three things end up pending:

my mother has to review three pinned posts, the Instagram account still needs to
be switched to professional, and the intake form asks for data we shouldn't
collect. Claude records all three as tasks and they show up in the Progress panel.

1. On Thursday I reopen that same chat. The Progress panel is empty. The three tasks

are still open — nothing was completed — but the panel only renders tasks touched
in the current exchange, so it shows nothing.

1. To see them I have to type "pendientes" and have Claude list them again. And

because a status-only update renders as Task #15 with no text, Claude has to
rewrite each task's subject just to make it appear — re-emitting information that
never changed.

1. With this feature, I'd open the chat and read the three items in two seconds,

the same way I'd glance at a whiteboard. That's the whole reason I want the panel:
it's the one place that answers "where was I?" without reading back through a
long conversation.

1. It would save me time because today the panel doesn't answer that question — so I

maintain a separate markdown file in the project as a backup list, and now I have
two lists that drift apart and have to be reconciled by hand.

Additional Context

Environment: Claude Desktop (Cowork mode), Windows, app version 1.52386.3.0.

Related issues I found while searching, none of which cover this:

• #51145 — Progress widget doesn't refresh after tasks are deleted (closed as

duplicate). Opposite symptom: tasks that stay too long rather than disappear.

• #76537 — sticky/pinned todo list. Scroll position within one session, not

persistence across sessions.

• #81120 — tasks in a project can't see other chats. Memory/context, not the panel.

Note on scope: per-chat scoping is the part that already works well for me —
I don't want one shared list across the project. This is only about a chat's own
open tasks surviving until they're closed.

Environment: Claude Desktop (Cowork mode), Windows, app version 1.52386.3.0.
Observed on Windows, but I have no reason to think this is platform-specific —
#51145 describes the same panel on macOS.