If you haven't installed yet, start at Add to Claude — it walks both paths step by step. This page picks up afterward.

In Cowork (claude.ai, Desktop, mobile)

Setup added the learning-with-court plugin and connected it. Nothing lives on your machine — the workshop runs in your Claude session, in the cloud.

To start, open a new chat and say "I want to start a workshop". The connected tools list what's available and ask which one. From there the guide walks each lesson and you direct it — you decide what to build and when to move on. There's no directory to find and nothing to run; the conversation is the workshop.

In Claude Code (terminal)

Setup put two things on your machine, and they do different jobs.

• lwc — a command-line tool you run in your terminal. Discover workshops, install them, manage secrets, switch between dev and prod. Examples: lwc catalog, lwc setup <id>, lwc env set ANTHROPIC_API_KEY, lwc list.
• The Claude Code plugin — runs inside Claude Code (your coding agent). When you say something like "start a workshop", the plugin reads lwc catalog and walks you through picking one. You don't run plugin commands in your terminal; you talk to Claude.

Start a workshop

Open Claude Code anywhere and type "I want to start a workshop". The plugin lists what's available and asks which one. It then drives lwc setup for you and tells you where to cd next. Or do it by hand:

lwc catalog                 # see the list
lwc setup <workshop-id>     # install
cd ~/learning-with-court/<id> && claude

lwc setup clones the workshop repo to ~/learning-with-court/<workshop-id>/ and runs pnpm install. If the workshop needs an API key (most code workshops do — see /secrets), it prompts for it with a hidden input. When it's done it prints the path; you cd there and run claude. Once you launch, the workshop's skills load automatically — say "let's start lesson 1" and the agent walks you through one step at a time, including hands-on edits in your own editor.

A note on costs

Workshops may ask you to use services that bill for usage — LLM APIs, cloud infrastructure, third-party SaaS. Anything you set up runs against your accounts, not ours. See /cost before you start.

First-walk friction points

The most common stalls and where to read more:

• "Where do I put my API key?" → /secrets
• "How do I edit a file?" → /editor
• "Something errored, what now?" → /troubleshooting
• "Who pays for what I set up?" → /cost