Feature request: read-only API for claude.ai conversation history

Use case

Claude Code users who use claude.ai heavily have no programmatic way to access their own conversation history. This makes it impossible to give Claude Code persistent awareness of past conversations without manually copy-pasting or reverse-engineering internal frontend APIs.

What we'd want

A read-only REST endpoint scoped to the authenticated user's account, returning conversation metadata (title, timestamp, ID, maybe a short summary). Something like:

GET https://api.claude.ai/v1/conversations
Authorization: Bearer <user_token>

This would enable:

• MCP servers that expose conversation history to Claude Code as a queryable tool
• Persistent cross-session context without manual effort
• Personal tooling and workflows built on top of your own data

Why this matters for Claude Code specifically

Claude Code is positioned as a persistent, context-aware coding assistant. But context resets every session. Conversation history is the most natural source of continuity — what projects you've been working on, what decisions you've made, what you've already explored. Without API access to it, that continuity has to be manually maintained.

Prior art

OpenAI exposes conversation history via their API. GDPR already requires data portability for EU users. This feels like infrastructure that likely exists internally and just needs to be surfaced.