[FEATURE] Enable Claude Code to report session progress to Web Chat

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

🔄 Enabling Claude Code to report session progress to Web Chat

Executive Summary

Enable Claude Code to post session summaries and project updates to Claude web chat, creating a persistent project management layer that complements Code's ephemeral tactical work sessions.

---

💔 The Problem

Claude Code: Excellent for focused coding sessions, but loses all context after each session ends. Every new session starts from scratch.

The issue: Projects aren't just about coding. They require design thinking, feasibility studies, architecture discussions, and strategic planning - work that happens between coding sessions. Claude Code's command-line interface is optimized for building, but it's not the right environment for exploring ideas, discussing trade-offs, or thinking through "what if" scenarios.

Claude Web Chat: Perfect for exploratory conversations, design thinking, and strategic planning - but has no awareness of what's actually been built in Code sessions.

Result:

• Users lose project continuity between tactical (Code) and strategic (Web Chat) work
• Design decisions made in web chat never inform Code sessions
• Progress made in Code sessions is invisible during planning conversations
• Team collaboration is broken - non-technical stakeholders can't see what's been built
• Users must manually bridge the gap, copy-pasting context back and forth

Proposed Solution

✨ The Solution : Enable Claude Code to report progress back to web chat, where:

For individual developers:

Web Chat becomes your "project manager" - aware of what's built, helping you plan next steps
You can explore feasibility questions and design ideas with full context of current implementation
Strategic thinking happens in the comfort of web chat, informed by actual progress

For teams:

Share progress reports - non-technical stakeholders (managers, designers, PMs) can follow a shared web chat that receives Code updates
They see what's been built without needing terminal access or technical knowledge
Real project management: stakeholders track progress, developers get feedback, everyone stays aligned

User Workflow

# End of coding session
claude-code --report "Completed user authentication, next: API integration"

# Or automatic on session end
claude-code --auto-report

This posts a structured summary to a designated web chat, where:

• Memory feature captures long-term project knowledge
• User can discuss strategy, priorities, and next steps
• Context persists across all future Code sessions

🛠️ Technical Implementation Options

Option 1: Simple HTTP Bridge

• Code generates markdown summary
• POSTs to internal Anthropic endpoint
• Authenticated via existing claude.ai session token
• Appears as new message in designated chat

Option 2: Shared Context Layer

• Code and Web Chat both read/write to shared project context store
• More ambitious but enables true bidirectional sync
• Web Chat decisions automatically inform next Code session

Option 3: Hybrid File + Manual

• Code writes to standardized claude-project-notes.md
• Web UI detects and offers to import these files
• Lower development cost, still improves workflow

🎁 User Benefits

• Continuity: Project memory survives Code session restarts
• Strategic oversight: Web Chat Claude tracks decisions, trade-offs, technical debt
• Better planning: "Manager Claude" helps prioritize next Code session goals
• Audit trail: Automatic documentation of what was built and why
• Learning: Memory feature captures project-specific patterns and preferences

💼 Business Benefits for Anthropic

• Differentiation: Unique multi-modal AI workflow no competitor offers
• Stickiness: Deeper integration between products increases retention
• Usage: Encourages more Code sessions (knowing progress is tracked)
• Showcase: Demonstrates agentic AI working at multiple abstraction levels
• Enterprise appeal: Project continuity is critical for professional developers

🛡️ Privacy & Control

• Opt-in feature (disabled by default)
• User chooses which chat receives reports
• Can disable per-project or globally
• Reports contain only what Code would show in terminal (no hidden data)
• Respects existing memory settings (user can disable memory entirely)

Alternative Solutions

Maybe related ?

Issue #17195 discusses syncing Web Chat Projects → Code (inverse direction). This proposal sounds like it could be related, maybe complementary but unfortunately is confusing in it's actual report.

Priority

Low - Nice to have

Feature Category

API and model interactions

Use Case Example

Example Report Format

## Claude Code Session Summary
**Date**: 2026-01-09 14:30  
**Duration**: 45 minutes  
**Project**: authentication-service

### Completed
- Implemented JWT token generation and validation
- Added password hashing with bcrypt
- Created user registration endpoint

### Decisions Made
- Chose JWT over sessions for stateless API design
- Set token expiry to 24 hours (configurable)
- Using bcrypt cost factor of 12

### Challenges
- Initially had TypeScript type errors with jwt.sign()
- Resolved by properly typing the payload interface

### Next Steps
- Add refresh token mechanism
- Implement rate limiting on auth endpoints
- Write integration tests for auth flow

### Files Modified
- src/auth/jwt.ts
- src/routes/auth.ts
- src/models/user.ts

Additional Context

_No response_