Playground Flow

Workbench starts from a playground id, connects it to Claude or Codex, and turns the session into a guided local build.

Start from a playground

Open the Workbench desktop app and search for the playground id shown on the playground page.

Workbench uses that id to load the guided build and prepare the local session around it. Then it gives the selected agent the lesson context it needs to tutor the student through the project.

Choose the agent

Workbench can use Claude or Codex as the coding agent for the session.

The agent is still the engine that reads, edits, explains, and reasons about code. Workbench turns that engine into a course tutor by keeping it attached to the playground state and the student's current step.

Work with the tutor

Workbench gives that interaction a clearer frame:

  • The active lesson step stays visible.
  • The task list shows what has been completed.
  • The tutor can explain what the student should understand before coding.
  • Code changes can be reviewed as the build progresses.
  • The session can move between manual work and agent-assisted implementation.

Inspect progress

Treat each step as something you can verify, not just accept.

Use Workbench to check what changed, compare the current state with the task, and decide whether to continue, ask the tutor for a correction, or bring in a reviewer agent.

Continue from setup

If you have not connected the local learning tools yet, start with Quick Start.

The full setup path prepares the launcher and MCP server before you run a complete playground in Workbench.

If you have questions, visit our Discord