Feature Request: Conversation History API for cross-client continuity (Claude App ↔ Claude Code)

Summary

It would be incredibly useful if Claude Code CLI could access conversation history from the Claude App (web/mobile), and vice versa. Currently, these two clients are completely siloed — conversations in one are invisible to the other.

Problem

• When I have a deep conversation in the Claude App about a topic, I can't continue or reference it in Claude Code CLI.
• Claude Code CLI has access to my local filesystem, MCP servers (Gmail, Slack, Google Docs, BigQuery, etc.), and powerful tools — but it has zero context about what I've discussed in the Claude App.
• This forces me to manually copy-paste context between clients, which defeats the purpose of having an intelligent assistant that knows me.

Proposed Solution

1. Conversation History API — Expose an API that allows authorized clients to read/search conversation history across Claude surfaces (App, CLI, etc.)
2. Cross-client conversation continuity — Allow Claude Code CLI to reference or continue a conversation started in the Claude App, and have CLI conversations sync back to the App.
3. MCP-compatible design — If the API follows MCP patterns, the community could build MCP servers to bridge the gap, enabling flexible integrations.

Use Cases

• "Hey Claude Code, remember what we discussed about X in the app yesterday? Let's implement that."
• Searching past app conversations for decisions, requirements, or ideas while working in CLI.
• Having a unified conversation history regardless of which client was used.

Why This Matters

Claude's value compounds with context. The more Claude knows about prior conversations and decisions, the more useful it becomes. Siloed clients break this compounding effect. A shared conversation layer would make the entire Claude ecosystem significantly more powerful.

---

Submitted from Claude Code CLI