Skip to content
Claude for Operators

Setting Up Persistent Workspaces

Last verified: 14 April 2026 | Applies to: Pro, Max, Team, Enterprise (desktop only)

In 30 seconds

Section titled “In 30 seconds”

Cowork Projects turn Claude from a blank-slate chat into a persistent work environment. Each project links to specific local folders, has its own custom instructions, can store per-project memory, and supports recurring tasks. Instead of re-explaining your context every session, you open a project and Claude already knows your files, your preferences, and your workflow. Think of it as a dedicated desk for each area of your business (month-end close, client proposals, content production, hiring), each one set up exactly the way you need it.

What it does

Section titled “What it does”
graph TD
    A[Create project] --> B[Link local folders]
    A --> C[Add custom instructions]
    A --> D[Set up recurring tasks]
    B --> E[Claude accesses project files]
    C --> E
    D --> F[Tasks run automatically]
    E --> G[Per-project memory builds over time]
    F --> G

A Cowork Project gives you:

  • Linked folders. Point Claude at specific directories on your machine. Claude can read, create, and modify files in those folders without you uploading anything manually.
  • Custom instructions. Persistent rules that apply every time you open the project. “Always use Australian accounting standards.” “Format reports in our company template.” “Refer to clients by their code names.”
  • Per-project memory. Claude remembers context specific to this project across sessions. Your month-end close project remembers your chart of accounts. Your proposals project remembers your pricing structure.
  • Recurring tasks. Schedule tasks that run within this project’s context. A weekly report that pulls from this project’s linked folders and follows this project’s formatting rules.

How to set it up

Section titled “How to set it up”

Step 1: Create a project

Section titled “Step 1: Create a project”

In Claude Desktop, open Cowork and click New Project (or type /project create). Give it a clear name: “Month-End Close”, “Client Proposals”, “Content Production”.

Section titled “Step 2: Link folders”

Click Add Folder and select the directory on your machine that contains the relevant files. You can link multiple folders:

  • A finance project might link to /Documents/Finance/ and /Documents/Reports/
  • A proposals project might link to /Documents/Proposals/ and /Documents/Templates/

Claude can now read and write files in these folders without you uploading anything.

Step 3: Add custom instructions

Section titled “Step 3: Add custom instructions”

Click Instructions and add the rules Claude should follow in this project:

This is our month-end close workspace. Rules:
- We use Australian Accounting Standards (AASB)
- Our fiscal year ends 30 June
- Always format currency as AUD with two decimal places
- Our chart of accounts is in /Documents/Finance/chart-of-accounts.csv
- When creating journal entries, use the format: date, account code, account name, debit, credit, description
- Save all workpapers to /Documents/Finance/2026/close-packages/

These instructions persist across every session in this project. You never need to repeat them.

Step 4: Set up recurring tasks (optional)

Section titled “Step 4: Set up recurring tasks (optional)”

If this project has regular cadences, schedule them:

/schedule every 1st of the month at 9am: Start the month-end close checklist. Load the previous month's close package for reference and create a new checklist for this month.

The task runs within this project’s context, using its linked folders, custom instructions, and memory.

Template workspaces

Section titled “Template workspaces”

Here are four project setups that cover the most common operator needs. Use them as starting points and customise.

Month-End Close

Section titled “Month-End Close”

Linked folders: /Documents/Finance/, /Documents/Reports/close-packages/

Custom instructions:

Month-end close workspace. We use [AASB/IFRS/GAAP]. Fiscal year ends [month].
Chart of accounts: [linked file path].
Standard reconciliation accounts: cash, AR, AP, prepaid expenses, accrued liabilities.
Save all workpapers to the close-packages folder with naming: [YYYY-MM]_[document-type].
Always include a reconciliation summary and variance analysis in the close package.

Recurring task: /schedule every 1st at 9am: Generate this month's close checklist from the template.

Client Proposals

Section titled “Client Proposals”

Linked folders: /Documents/Proposals/, /Documents/Templates/, /Documents/Pricing/

Custom instructions:

Proposals workspace. Our standard pricing is in the Pricing folder.
Use the proposal template from the Templates folder as the base format.
Always include: executive summary, scope of work, timeline, pricing (itemised), terms.
Client names should appear at least 3 times in the executive summary (personalisation matters).
When creating a new proposal, ask me for: client name, project scope, timeline, and any special terms.

Recurring task: none typically. Proposals are ad hoc.

Content Production

Section titled “Content Production”

Linked folders: /Documents/Content/, /Documents/Brand/

Custom instructions:

Content workspace. Brand guidelines are in the Brand folder.
Voice: professional but conversational. Australian English.
Standard content types: blog posts (800-1200 words), newsletter issues (500-700 words), social posts (under 280 characters for X, under 300 for Bluesky).
Always check the content calendar in /Documents/Content/calendar.csv before creating new pieces.

Recurring task: /schedule every Monday at 9am: Review the content calendar for this week and create a production checklist.

HR Documentation

Section titled “HR Documentation”

Linked folders: /Documents/HR/, /Documents/Templates/HR/

Custom instructions:

HR workspace. Use Australian employment law references (Fair Work Act).
Templates for offer letters, position descriptions, and performance reviews are in the Templates/HR folder.
Always use gender-neutral language.
Salary ranges and benefits are in /Documents/HR/compensation-bands.csv. Reference but never share externally.
For position descriptions, always include: role summary, key responsibilities, required qualifications, and reporting structure.

Recurring task: /schedule every Monday at 9am: Check for any position descriptions that haven't been updated in 6 months and flag them.

Per-project memory vs global Workplace Memory

Section titled “Per-project memory vs global Workplace Memory”
graph LR
    A[Global Workplace Memory] --> B[Available in ALL projects]
    C[Per-project memory] --> D[Available in THIS project only]
    A --> E[Company name, team members, general preferences]
    C --> F[Project-specific context, history, decisions]

Global Workplace Memory (set up via the Workplace Memory workflow) carries into every project. Use it for company-wide context: your team members, your company name, your general preferences.

Per-project memory builds automatically as you work within a project. Claude remembers decisions, context, and patterns specific to that workspace. Your month-end close project remembers that you always adjust for the prepaid insurance amortisation. Your proposals project remembers that Client X prefers detailed timelines.

You do not need to choose between them. They layer. Global memory provides the foundation; per-project memory adds the specifics.

How operators actually use it

Section titled “How operators actually use it”
Section titled “Related”

Something wrong or outdated? Let us know →

Get weekly workflows. Subscribe to the newsletter.