Project-scoped inter-chat continuity / chat handover for RAG projects

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:
Claude Projects encourage splitting work into multiple topic-based chats (for organization and to manage context window size). But chats within a project don't share context with each other — only the static KB files do. This creates a real workflow bind:

• Keep one long chat → context bloat, higher token cost, degraded performance
• Split into topic chats → lose accumulated decisions, outputs, and reasoning from prior chats

This defeats the purpose of organizing work thematically inside a project.

Proposed solution:
A lightweight chat handover / summary mechanism at the project level:

• When a chat is closed, archived, or manually triggered, Claude auto-generates a structured summary (decisions made, outputs produced, open threads)
• That summary gets pinned to the project KB — or a dedicated "thread log" layer — and becomes available to subsequent chats in the same project
• This would preserve workflow continuity without reloading full conversation history

Why this matters:
Power users running multi-session, document-heavy workflows (content strategy, brand development, research) are currently forced to manually bridge chat gaps by copy-pasting prior outputs into the KB. That's friction that undermines the core value proposition of Projects.

Precedent: This is essentially what good human project management does — meeting notes feed the next meeting. Projects should support the same loop natively.

Proposed Solution

Proposed solution:
A lightweight chat handover / summary mechanism at the project level:

• When a chat is closed, archived, or manually triggered, Claude auto-generates a structured summary (decisions made, outputs produced, open threads)
• That summary gets pinned to the project KB — or a dedicated "thread log" layer — and becomes available to subsequent chats in the same project
• This would preserve workflow continuity without reloading full conversation history

Why this matters:
Power users running multi-session, document-heavy workflows (content strategy, brand development, research) are currently forced to manually bridge chat gaps by copy-pasting prior outputs into the KB. That's friction that undermines the core value proposition of Projects.

Precedent: This is essentially what good human project management does — meeting notes feed the next meeting. Projects should support the same loop natively.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

I am constantly requesting manula chat handover docs for:

1. Keeping context windows small
2. Organizing topics related the same project in a meaningful way

Additional Context

_No response_