Projects and sessions

When Claude works in your files and folders instead of in a chat. A project here is a folder with your files: history, memory and sessions that can be continued and handed over.

Track
2 · Work
Duration
about 5 hours
Modules
7 modules
Status
Planned

Who it is for

Power users, project managers and developers who know modules 1.1 and 1.2.

Modules

  1. Module 2.1Planned

    From chat to work in your files

    What you learn
    The difference between the chat, Claude Cowork (Claude does tasks in your files from the app) and Claude Code (Claude as a tool in a project folder, mostly for developers), and when each one fits.
    Exercise
    Let Claude tidy up a practice folder, and see exactly what was changed.
    What you have afterwards
    You know which tool fits which task.
  2. Module 2.2Planned

    First session in a folder

    What you learn
    A session is one conversation with Claude about a task in a folder: start it, give a task, follow along, and approve or undo the changes.
    Exercise
    Build a small quotation sheet in the practice folder from start to finish.
    What you have afterwards
    A completed session with a result you approved yourself.
  3. Module 2.3Planned

    History with Git and GitHub

    What you learn
    Git is the project's history: every saved step can be seen and rolled back. GitHub is the service where the history is shared and checked.
    Exercise
    Save three steps, roll one back, and put the project on GitHub.
    What you have afterwards
    A project with a history you can roll back.
  4. Module 2.4Planned

    The project's memory

    What you learn
    CLAUDE.md is the file that holds the project's rules, language and standard commands, so Claude reads them in every session.
    Exercise
    Write a CLAUDE.md for the practice project and see it work in a new session.
    What you have afterwards
    A memory file for your own project.
  5. Module 2.5Planned

    Sessions: continue, split, hand over

    What you learn
    Resume a session, keep it short, and pass the work on to a new session or a colleague.
    Exercise
    Interrupt a task, write a handover, and continue in a fresh session.
    What you have afterwards
    A handover template and a fixed routine.
  6. Module 2.6Planned

    Many sessions at once

    What you learn
    Run several sessions side by side, follow them from the phone, and keep them apart.
    Exercise
    Run two tasks at the same time in separate folders and follow them from the phone.
    What you have afterwards
    An overview of who is doing what.

    Note: On Team and Enterprise an administrator must first switch on remote control from the phone (Remote Control).

  7. Module 2.7Planned

    Recurring tasks on a schedule

    What you learn
    Let Claude run a task every morning or every week and tell you when something deviates.
    Exercise
    Set up a weekly report and have it delivered.
    What you have afterwards
    One recurring task that runs on a schedule.

    Note: Tasks on your own computer only run while it is on and the app is open. Tasks in the cloud are a preview.

Want to use the academy?

Tell me which roles you have and where you stand today. I will suggest a path through the courses: self-study, a workshop or a complete programme.