Claude.ai Projects review (2026): is it actually a Claude Code alternative?

I’ve used Claude.ai Projects daily for ~8 months across DotVA and content work. Here’s the assessment.

What it actually is

A Project is a persistent workspace in Claude.ai that holds:

• Custom instructions (a per-project system prompt, “You’re helping me draft content for an Australian Shopify skincare brand, our voice is X, our audience is Y…”)
• Uploaded knowledge files (PDFs, CSVs, docs that the model can reference in every conversation)
• A history of conversations within that project

Every new chat within the project starts with all of that loaded. You’re not re-explaining context every time.

Where Projects wins

1. Persistent knowledge

For I have a “client editorial” project with:

• Our brand voice doc
• Our product list with descriptions
• Our content style guide
• Our top-performing past posts as examples

Every time I start a new chat in that project, Claude already knows all of it. I don’t paste the client’s brand voice doc into every prompt.

2. Multi-conversation memory

Different conversations in the same project share the underlying knowledge but stay separate. I can have “Q2 newsletter brainstorm” running in parallel with “April supplier email” in parallel with “next IG campaign concepts”, all leveraging the same client context, but each focused on their own work.

3. Bundled with Claude Pro

$31 AUD/month (Claude Pro subscription) gets you Projects + everything else Pro offers. No separate spend.

4. Clean non-developer UX

The web interface is polished. There’s no terminal, no config files, no CLAUDE.md to maintain. For an Australian small-business owner who isn’t a developer, this is the gentlest possible entry to “AI as a workspace.”

Where Projects loses (to Claude Code)

1. No filesystem access

Projects can’t read files from your computer or write back. You upload files; the model reads them; you copy outputs back manually. Claude Code reads + writes your filesystem directly.

For “edit this CSV in place” or “scaffold these 30 new files” workflows, Projects is the wrong tool.

2. No MCP / tool connections

Claude Code lets you wire Claude into Xero, Shopify, Slack, Notion, Postgres, GitHub via MCP. Projects doesn’t (yet). The model can read documents you upload, but it can’t call out to your business systems.

3. No script / command execution

Projects can write you a Python script. It can’t run it. Claude Code can.

4. Limits per project

There’s a file count + size limit per project (~20 files, ~200k characters total at time of writing, changes over time). For knowledge bases bigger than that, you’ve outgrown Projects and need RAG.

A real Australian use case

Where I use Projects daily:

• client editorial: blog drafts, email newsletter copy, social captions
• DotVA client onboarding: drafting kickoff docs, scoping conversations
• On Autopilot content: brainstorming article angles, refining outlines

Where I switch to Claude Code:

• Editing actual files in the Shopify export
• Running the nightly inventory agent
• Writing this article you’re reading right now (drafted in Claude Code so I could also edit the Astro components live)

Who Claude.ai Projects is for

• Non-developer operators in Australian SMB
• Knowledge workers (consultants, marketers, writers, researchers)
• Anyone whose AI work is mostly thinking-and-writing, not doing-and-shipping
• Teams on Claude Team / Enterprise wanting shared project knowledge

Who it isn’t for

• Developers (use Claude Code)
• Anyone running scheduled agents (Claude Code in headless mode)
• Anyone needing to wire AI into business systems (Claude Code + MCP)
• Anyone needing >200k tokens of knowledge per project (build RAG)

Verdict + recommendation

Buy Claude Pro ($31 AUD/month). You get Projects + everything else Pro offers. Use Projects for the thinking-and-writing work. If you’re also a developer or running agentic background work, add Claude Code (metered, ~$40-150 AUD/month on top).

For non-developer Australian small business operators, Claude.ai Projects + Pro is the right starting point. Most operators get 6-12 months of value from it before they outgrow it into Claude Code or Anthropic API custom builds.