[FEATURE] an open-items window that's on by default and can be shared with other collaborators

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

Feature request: an open-items window that's on by default
In long working sessions, open questions, decisions and to-dos get buried in the chat. Each answer spawns new questions, and I end up scrolling back to find what's still unanswered.

Proposed Solution

I set up a pattern where Claude keeps every open item in a live side page instead (can also be an artifact which you can share with collaborators who have their own Claude account): each item has an ID (Q question, A action, D decision, F finding), who leads it, its status, and what it blocks. I can answer directly on the page, and each reply ends with one line saying what changed. It works far better than chat for multi-day projects. I'd like a setting that turns this on for every session, ideally as a built-in panel next to the conversation, so users don't have to build it themselves. And ideally in the session Claude is checking the state of the document /page to see if content has changed from the side of the user - OR better yet the user can save their reaponse and that triggers / prompts Claude to review the answer/status of that content. Thanks!

<img width="934" height="291" alt="Image" src="https://github.com/user-attachments/assets/ded1175f-08f6-44d6-8b97-30f479e0c1ef" />

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

• Working on the editorial copy of a design that Claude Code/ Claude Design built, getting feedback and copy changes into the working demo/content. Each piece of text from each section is labeled, and then the team can share the document with set people and they can each have an open task list - or be shown a task that needs their review after a collaborator provided their input/feedback - user can mark they approve/agree or propose a change and justify it - then when done Claude design would input it into the mock-up, file.
• In a long working session requiring multiple user decisions / actions - or even a short session - open questions and documented answers are all listed out for the user to review and provide feedback on, and if a situation changes they cal also change the response/have an adjustment made.

Additional Context

<img width="934" height="291" alt="Image" src="https://github.com/user-attachments/assets/98b4ad64-b03a-407e-bf71-caf1804107ec" />