DeSpain Consulting

Use the new Projects in Claude Code on real work

The setup, the context file template, and the exact prompts I used to hand my whole holiday prep to one project and four threads.

"Projects used to be folders. Now each one is a conversation that splits into threads."

In the Claude Code desktop app, a project is now one ongoing chat. You ask for things in the main chat, and Claude starts threads that work in parallel and report back. Every thread reads the same project notes, so an answer you give in one place reaches the rest.

I tested it on my gift business's holiday prep: a gift guide, a customer email, a social calendar, and a shipping FAQ. You do not need to write code. You do need the Claude Code desktop app and a clear goal.

What you need

The Claude Code desktop app, signed in to a paid Claude plan. Projects is in beta and rolling out by plan, so if you don't see it in your sidebar, check what your plan includes.

One real project with a finish line. Holiday prep, a launch, a newsletter series. Something with three or four pieces that depend on the same facts.

A short context file about your business (template in step 3).

Optional: Google Drive connected to your Claude account, if your product lists or notes live there.

1

Clean house, then upgrade

In the Claude desktop app, switch to the Code tab (the </> button at the top), then click Projects in the sidebar. It is marked Beta. Click Get started. Before it lets you in, it asks you to upgrade your existing projects or archive them. I had seven. I archived the four I'm done with and upgraded three. The upgrade runs in the background, so you can close the window and keep working.

2

Fill in the New project form

Click Create new project. There are three fields: Name, Goal, and Context. The examples in the form are written for developers, but nothing in it needs code or a repository.

The Goal is the most important line you will write. Name the finished pieces you want, so Claude knows what done looks like. Mine:

Goal fieldGet ahead of the holiday rush with a gift guide, a customer email, a social calendar, and a shipping and delivery cutoff FAQ, all in my voice.
3

Add a short context file

Under Context, click + Add. You can add a file, a folder, a repository, or a Google Drive folder. I wrote a short file about my business and added it as a file. Here is the template (fill in the brackets and save it as a text or Markdown file):

Context file template[Business name] is my [what you do] in [where]. I [what you sell and how it gets made]. [How it reaches customers: shipping, delivery, pickup]. [Your busiest season or biggest customer group]. Write in my voice: [three or four words that describe how you sound]. [Anything you never want in your writing]. Never invent prices, dates, or product details. Ask me when you need one.

Keep the last line. It is the reason my project asked me for dates and prices instead of making them up.

4

Let it suggest the threads

Click Create project and wait. Before I typed anything, Claude read my goal and context file and came back with four suggested threads: draft the gift guide, write the customer email, plan the social calendar, and write the shipping cutoff FAQ. Each had a one-line reason. It also told me it used my recent Claude sessions, so know that it can see those.

One click on Start 4 threads and all four ran at once. The gift guide thread searched my Google Drive, found my basket contents sheet, and built the guide from my real products. It left every price blank because it could not confirm my old prices were still current.

5

Answer once, in the thread it points you to

Three threads needed my shipping dates. The main chat noticed and told me to answer once, in the FAQ thread, and it would pass my dates to the other two. Rough answers are fine. Mine:

Type in the thread1. I ship with USPS, UPS, and FedEx. I don't offer an expedited or express option. 2. During the holidays I need 2 to 3 business days to build a basket before it goes to the carrier. 3. Last day to order for shipped delivery by Christmas is Monday, December 14. Corporate and bulk orders need to be in by Friday, November 13, about a month before that cutoff, so I have time to source from my Utah makers. 4. I hand-deliver in Park City, nearby towns like Kamas and Heber, and Salt Lake City. Last day to order for hand delivery is Tuesday, December 22, and my last delivery day is Thursday, December 24. 5. The studio is closed December 25 through 27. No international shipping. No perishables note needed this season.

The main chat confirmed it sent my dates to the email and social calendar threads. Then the FAQ thread caught a problem in my own dates. A December 14 order that takes three days to build ships December 17, the same day as the USPS Ground Advantage send-by date, which leaves no buffer for coast-to-coast ground.

6

Steer a thread when your plans change

Every thread has its own box at the bottom that says Steer this thread. I used it to split my cutoff and asked it to pass the change along:

Type in the threadLet's split the shipping cutoff. Keep Monday, December 14 as the last day to order for delivery in Utah and nearby states (Idaho, Colorado, Wyoming, Nevada, Arizona). For everywhere else in the US, the last day to order is Friday, December 11, so there's a buffer before the carrier deadlines. Please update the FAQ, and send the new date to the email and social calendar threads too.

It updated the FAQ, saved the new dates to the project notes, sent them to the other two threads, and checked that December 11 is a Friday.

7

Send project-wide changes to the main chat

When a change touches several threads, type it in the main chat instead of a single thread. I raised my price floor halfway through:

Type in the main chatMy prices changed: $88 is now my lowest price, and the bands are $88 to $128, $138 to $158, and $168 and up. Check the email and social calendar threads for the old $38 and $78 prices and update them.

It sent the change to both threads and told me up front there might be nothing to fix, since both drafts were written without prices. Both came back clean, and it offered one useful addition instead of busywork.

8

Edit the file yourself and hand it back

You do not have to describe every change in chat. I opened the gift guide draft, made my edits and notes right in the file, attached it back to the thread, and typed "updated guide". The thread read my edits, summarized what changed, and asked four short follow-up questions. Shorthand answers worked fine.

9

Check the Overview

Click Overview at the top to see every thread grouped by status: Waiting on you, Idle, and Resolved. A thread that wrote something it wants you to check stays open until you OK it. It will not mark itself done on work that needs your eyes.

Settings worth knowing

Click the gear next to Overview.

Memory: this is how the routing works. Project instructions work like a rulebook every new thread follows. Claude wrote mine on its own, and you can edit them. Below that, Claude keeps its own notes files that every thread reads, like my makers list and shipping dates. To change a note, tell it in plain English in the box at the bottom.

Environment: all of your claude.ai connectors are available in every thread, which is how mine reached Google Drive.

General: you can edit the goal, see the models (both the main chat and the threads ran Opus 5.5 in my project), turn on auto-continue so threads pick up when usage limits reset, and pause the project.

What it cost

The Usage tab showed 22.3 million tokens across the main chat and four threads. That sounds huge, but about 96% of it was cache reads, the threads re-reading the shared project notes, and the output was about 88,000 tokens. The app also gives up to $100 of initial usage, including the automatic setup, that does not count toward your usage limits, and my setup ran inside it. I don't have a dollar figure to share beyond that.

What's not available yet

Browser use: project threads can't use your browser or the sites you're signed into.

Cowork tasks on this computer: tasks you ran in the desktop app stay local, and a new project can't read them.

Want help setting up your first project?

We can write your goal and context file together and start your first threads in one hour.

Get Started with AI ($150)