---
id: "prereq-claude-cowork-access"
type: "prereq"
source_timestamps: ["00:02:58", "00:08:21"]
tags: ["software", "access"]
related: ["entity-claude-co-work", "concept-custom-connectors-mcp"]
reason: "Required for local file access and custom API connector integrations."
sources: ["mag"]
sourceVaultSlug: "claude-cowork-250-posts-engine-2026May14"
originDay: 4
---
# Access to Claude Co-Work or Claude Desktop

## Why This Is Required

The entire workflow demonstrated in this video relies on [[entity-claude-co-work|Claude Co-Work]] (or the Claude Desktop app with specific beta features enabled).

**Standard web-based ChatGPT or standard Claude web interfaces do NOT have:**

- Local file system access (you cannot ask web Claude to read `~/Downloads/receipts.jpeg`).
- [[concept-custom-connectors-mcp|Custom Connector (MCP)]] capabilities required for tools like [[entity-blotato|Blotato]].

## Enrichment Validation

The enrichment overlay confirms: as of 2025–2026, Anthropic concentrates deeper system integration (tools, filesystem, APIs) in **Claude Desktop + MCP**. The standard web UI supports file uploads but not arbitrary local filesystem listing or arbitrary MCP servers.

Similarly, OpenAI's richer tools (Assistants API, custom tools) target API/programmatic clients, not casual web UI users.

## Implication

If you cannot install Claude Desktop, you cannot run the [[framework-content-automation-workflow|End-to-End Claude Content Automation Workflow]] as described. Alternative architectures would require building your own orchestration layer with the Claude API + custom code.


## Related across days
- [[prereq-claude-desktop]]
- [[claim-local-execution-efficiency]]
- [[arc-local-first-claim]]