Claude Projects vs Claude Code: Read/Write Gap Frustrates Second Brain Users

A Reddit user describes maintaining a "second brain" filesystem as markdown files—personal todos, short/long-term goals, journal entries—integrated with calendar and Gmail. They started with Claude Code as the interface and file read/write layer, but after Claude Chat's voice feature launched, they created a Claude Project with a snapshot of those files for on-the-go access. The voice access worked well, but updating files became painful: files go stale quickly. Their workflow: have a productive chat session, ask for a conversation summary, paste that summary into Claude Code to edit the files, then paste the updated files back into the Claude Project. This requires a weekly manual sync session.

Key Pain Points

• Claude Chat (Projects) can only read snapshots, not edit the source files.
• Claude Code has native read/write access to the filesystem, but lacks voice input.
• The manual round-trip (Chat → summary → Code → edit → upload to Project) is friction-heavy.
• Snapshots become stale quickly, reducing usefulness of voice queries.

Proposed Workaround

The user is considering building an MCP (Model Context Protocol) server to host the files and give Claude Chat read/write access, but calls it "overkill" given their setup. They wish Anthropic would let Claude Chat edit Project files the same way Claude Code does—handling both reading and writing natively without glue code.

For developers running similar personal knowledge management (PKM) systems with Claude, the gap between Claude Chat's voice convenience and Claude Code's file operations remains a sticking point. An MCP server could bridge this, but adds infrastructure overhead. A simpler fix from Anthropic—enabling file writes in Claude Projects—would eliminate the weekly sync chore.