Claude Projects Read/Write File Capabilities

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

MEMORY SPRING
AI Consulting & Training
memoryspring.com

RE: Feature Request - Read/Write File Capabilities in Claude Projects

Dear Anthropic Product Team,
I'm writing to share a field observation that I believe has significant implications for Claude's adoption in enterprise environments - and to propose a feature that would remove what we've found to be the single largest barrier to deployment.

Who We Are
Memory Spring is an AI consulting firm specializing in enterprise deployment of Claude for the Architecture, Engineering, and Construction (AEC) industry. We are currently building "ProposalBot" - a proposal coaching and drafting system that uses Claude Projects as its application platform - for Teichert Construction, a Claude Enterprise customer. Our goal is to make this a repeatable, scalable solution across the AEC sector.

The Constraint We Encountered
Claude Projects is an excellent platform for building AI-powered applications. The ability to upload instruction files, define a persona, and create a persistent knowledge base is genuinely powerful. We chose it as the foundation of our system precisely because of these strengths.

However, we discovered a series of fundamental limitations:

• Claude Projects treats all uploaded files as read-only.
• There is no mechanism to edit, update, rename, or delete files in place.
• No download button on file previews.
• No text editor.
• No version management.
• Flat file structure - no folders.

Every file modification requires a manual cycle of copy-to-external-editor, edit, delete old version, and re-upload.
For a system that depends on a living, curated knowledge base - where proposal content is continuously drafted, reviewed, refined, and promoted - this creates 100% file redundancy. Every file must be maintained in two places: wherever users can actually edit it, and in the Claude Project where the AI can access it.

What This Forced Us to Do
This single limitation required a complete architectural pivot. We redesigned our system from a model where Claude Projects served as both the AI platform and the content repository to a hybrid architecture where:

• Claude Projects retains the AI application layer (instruction files, persona definitions, coaching methodology) - content that benefits from being read-only.
• Microsoft OneDrive/SharePoint becomes the source of truth for all proposal content - because that's where users can actually edit files using tools they already know.
• The M365 MCP connector bridges the gap, giving Claude read access to OneDrive. This works, and we're grateful it exists in Enterprise, but NEEDS to exist in Max and Pro. But it is a workaround for a gap that shouldn't exist in the first place. The connector is read-only, so Claude still cannot save outputs back to OneDrive - every deliverable must be downloaded from the chat and manually saved by the user.

This will become tedious for the users. It is like having two kitchens on separate sides of a building and having to carry creations back and forth to prepare them before serving them. Imagine the potential for failure!

The Feature Request
We respectfully request that Anthropic add basic file management capabilities to Claude Projects. Specifically:

- In-place file editing - the ability to open, modify, and save files directly within the Claude Projects interface, even if limited to text-based formats (.md, .txt, .json).
- File download - a download button on file previews so users can pull files out without the copy-paste workaround.
- File replacement/versioning - the ability to replace an existing file with an updated version without deleting the current one and re-uploading.
- Write-back via M365 connector - the ability for Claude to save files directly to OneDrive/SharePoint, completing the round-trip that the current read-only connector starts.
- Folders in a Project - The ability to create folders in a Project is a critical construct for managing different types of data consistently.

We understand the safety rationale for read-only defaults. We're not asking for unguarded write access. Permission-gated, user-confirmed write operations - consistent with Claude's existing human-in-the-loop principles - would fully address our needs while preserving safety boundaries.

Why This Matters Beyond Our Project
The AEC industry represents a $13 trillion global market where proposals are the lifeblood of revenue. Every general contractor, engineering firm, and architecture practice builds proposals from curated libraries of reusable content - bios, project descriptions, safety narratives, technical approaches. This is exactly the use case Claude Projects was designed for.

But AEC firms are Microsoft 365 shops. Their teams edit documents in Word. They collaborate through SharePoint. They don't know Markdown and their IT departments won't approve new editing tools for a pilot AI project. When Claude Projects can't participate in the document lifecycle - when it's limited to receiving files but never giving them back in a manageable way - it creates friction that enterprise buyers will use as a reason to choose a competitor.

We are committed to building on Claude. We chose this platform deliberately because of Anthropic's approach to safety, the quality of Claude's reasoning, and the potential of Projects as an application layer. We want this to work. We're asking for the tools to make it work without architectural workarounds that add complexity for our clients.

We're Happy to Help
If this is on your roadmap, we'd welcome the chance to be an early tester or provide feedback from the field. If it's not yet on your roadmap, we hope this letter helps make the case. Our experience is that Claude Projects is 80% of the way to being an extraordinary enterprise application platform. The missing 20% is file lifecycle management, and it's the 20% that determines whether enterprise teams can adopt it without IT workarounds.

We appreciate your time and your work. Claude is a remarkable product, and we're building our business on it. We just need it to close the loop.

_With respect and enthusiasm,_
_Bud_
Robert Bud James III, PhD
Sr VP Curriculum Development and Master Instructor
[Memory Spring] (https://memoryspring.com/)

Proposed Solution

See the Problem Statement

Alternative Solutions

See the Problem Statement

Priority

Critical - Blocking my work

Feature Category

File operations

Use Case Example

See the Problem Statement

Additional Context

_No response_