Opens in a new tab
Skip to main content
Lesson 10 of 10

Start the Next Session Clearly

Use a short opening request that reconnects the goal, source and remaining decision.

About 10 minutesNo coding experience neededExplore in your browser

Look around. Try a small click.

This lesson works as a written guide with interactive examples. You can explore here before opening the real application or provider dashboard. A recorded video has not been added yet.

Read the short lesson

What will make more sense

  • Start a session with current sources and one immediate task.
  • Update the handover with verified state rather than assumptions.

One idea to keep

Begin with current sources, do one clear task and leave an honest handover.

The short lesson

Read the explanation at your pace

A useful next session can start with a small routine. Name the project, point to the current overview and handover, then state the immediate task. You do not have to repeat the whole project history. You also do not have to trust that the assistant already remembers it. The current files give both of you something concrete to read and verify.

For Willow Workshop, a next request could be: read project-overview.md and handover.md, confirm the current fact source, then review the invitation draft for tone only. Keep the event details and draft-only boundary unchanged. This request connects the previous work to one new action. It does not invite the assistant to restart the project or distribute the message automatically.

Before editing, ask for a brief state report if anything is uncertain. The assistant might say that the fact sheet is current, the invitation is a draft and approval remains with the owner. If it instead claims the invitation was sent, you have a mismatch to resolve before continuing. A small source check can prevent a much larger chain of mistaken assumptions.

At the end, update the handover only with what actually happened. If the tone was reviewed but not approved, say that. If a fact changed, update the controlling source through the agreed process instead of hiding the new fact in chat. The next session should not have to search three conversations to discover which time or capacity now applies.

You now have a simple abstraction for project memory: a current source for facts, supported instructions for the way of working, selected context for the immediate task and a handover for resuming. Provider memory may help, but it is a separate feature with its own controls. None of these removes the need to review a consequential result.

The final activity asks you to choose a clear opening request. After that, you can continue to Agent Files and Reusable Skills for supported instruction methods, or Everyday Documents for practical drafting. There is no requirement to build a complex memory system first. A few readable files, clear roles and a small review habit are enough to make your next AI session more useful.

Try it here

Try it here · no installation needed

Start the next session

Explore the prepared example, then choose a response. Your choice reveals its explanation immediately.

This is a local learning example with prepared responses. It does not run VS Code or contact an AI service.

Continue everything from before.

Which opening request gives the next assistant a useful boundary?

A tiny next step, if you want one

Optional: try 2 small actions at your own pace

You can finish this lesson by exploring the example above. These real-app actions are optional, and there is nothing to submit.

  1. Optional: follow the file references in handover.md once more.
  2. Optional: copy the prepared next-session request into a draft note without sending it.

A quick confidence check

These checkmarks are a personal reminder. Choose what feels familiar, and come back whenever you want.

Your place is saved in this browser when storage is available. There is no grading or account sync.

Try a short question

Choose an answer to see why it fits. You can try again or explore every explanation.

Where should a newly approved session detail be maintained?

What is enough to begin a useful project memory routine?

If something looks different

The next assistant reads a handover but disagrees with the current file.

Ask it to name the conflicting evidence. Resolve the current state before approving edits based on the old note.

Keep learning

Keep learning with another focused course. Each has its own written lessons, examples and prepared files.

Organize your work

Agent Files and Reusable Skills

Turn your working methods into supported project instructions and small SKILL.md packages that an assistant can use and you can review.

10 written lessons · Guided browser activities · Free to read

Explore this course
Connect your tools

API and MCP Connectors

Understand how an assistant connects to business services, what APIs and MCP do, and how to use a connected source clearly in a session.

10 written lessons · Guided browser activities · Free to read

Explore this course

Sources and further help

Read the official product guidance and related learning resources when you need them. You do not need to read every reference now.