Projects & Artifacts — turn Claude into your workspace

Introduction

Regular chat is like talking through a crack in the door: you ask, Claude answers, and then everything flows down and disappears. To edit a draft, you copy it out, make changes, paste it back — repeating this until you're exhausted. Projects and Artifacts were created to transform that crack into a real workspace.

This article — the third in the series — introduces two components that make up that workspace: Artifacts (the tabletop where you create and edit products on the spot) and Projects (the drawer that holds long-term context). By understanding both, you will stop using Claude as a chat box and start using it as a workspace.

Pure chat is like a messy desk

In pure chat, everything exists in a single flow: questions, answers, drafts, edits, all mixed together and scrolling away. Finding an old draft is a real ordeal, and you have nowhere to "set" the product down and make it presentable.

• Products and conversations blend together, lacking separation.

• To edit, you must copy it out and paste it back, losing continuity.

• Context disappears every time you start a new chat.

What are Artifacts — a workspace alongside the chat frame

Artifacts are a separate frame that appears next to the conversation, where Claude places independent products: a document, a code snippet, a table, a page. You can view and edit directly in that frame, while the chat beside it is for commands and discussions.

• Products are separated from conversations: easy to view, easy to edit, easy to retain.

• Edit repeatedly right on the spot, without copying out.

• Suitable for everything to take shape: articles, plans, code, tables.

What are Projects — a place to hold long-term context

Projects are a persistent space that holds guidelines and foundational documents for an entire workflow, so that all chats within it share the same context. The article "Claude Project like a pro" delves into this; here, you only need to grasp its role in the workspace.

• Maintains context: you don’t have to reintroduce "who I am, what the project is" every time.

• Consolidates related work in one place instead of scattering it across various chats.

• Serves as the foundation for Artifacts to emerge in the right tone and context.

The two components combine to form a workspace

A simple visualization: Projects are the drawer and document shelf that hold everything related; Artifacts are the tabletop where you actually work and refine products. Together, Claude is no longer just a chat box but an organized workspace.

• Projects maintain context; Artifacts are where products take shape.

• You open a Project, create multiple Artifacts within it, all in the same flow.

• The result: seamless work instead of disjointed Q&A.

Working on Artifacts: edit in place instead of copying out

The greatest strength of Artifacts is the immediate editing loop. You don’t have to describe the entire draft again; you just point directly to it and tell Claude to fix the specific part.

• "Shorten the introduction to half, keep the conclusion intact."

• "Change the tone of the entire piece to be friendlier."

• "Add a section about costs after the planning part."

When to use Artifacts, when to just chat

You don’t always need to open the tabletop. Distinguish to avoid complicating simple tasks.

• Use Artifacts when there is a product that needs to be created, edited multiple times, or retained.

• Just chat when you need to ask a quick question or clarify an idea.

• Long-term and repetitive tasks should be wrapped in a Project for clarity.

A working session on the Claude table: example

Situation: you need to draft a collaboration proposal and revise it through several rounds.

• Open a Project "Proposal for Client X", load the brief and standard proposal template.

• Ask Claude to generate the proposal — it appears as an Artifact alongside.

• Edit on the spot through several rounds: trim excess parts, add a pricing table, change the tone.

• Keep that Artifact in the Project to reopen and continue later, maintaining continuity.

5 mistakes that turn your workspace into a cluttered mess

• Doing everything in plain chat, never opening the Artifact to tidy up.

• Copying the product outside to edit and then pasting it back, losing the in-place loop.

• Stuffing unrelated tasks into one Project until it becomes confusing.

• Not naming the Artifact and Project, making it hard to find again after a few days.

• Opening the Artifact for trivial questions, complicating simple tasks.

Results you get after this lesson

• A real workspace in Claude, instead of a fleeting Q&A dialogue.

• The in-place editing loop helps shape the product faster and more neatly.

• Context is preserved, allowing for long-term work without starting over from scratch.

Steps to set up your Claude workspace this week

• Choose a product you are currently working on, ask Claude to generate it as an Artifact.

• Practice editing on the spot: issue three commands to adjust the right places instead of copying outside.

• Create a Project for that workflow, load the brief and foundational documents.

• Clearly name the Project and Artifact so you can easily reopen and continue next time.

Conclusion

As long as you see Claude as a dialogue box, you will continue to struggle with copy-pasting and starting over every day. Artifacts provide you with a workspace to create and edit products on the spot; Projects give you drawers to maintain context throughout. By combining the two, Claude becomes a true workspace — a place where ideas take shape, are refined, and stay. Set up a corner of your desk like that, instead of just talking through a crack in the door.