For bootcamp instructors

A coding lab is thirty people working at wildly different speeds on material where being stuck is invisible until someone admits it. Workshopy gives you the lab as a live session: the exercise is a Markdown file with code blocks, each student marks each step in progress, done or stuck, and your dashboard shows the whole cohort at once. Across cohorts, the reports tell you which step keeps breaking people — which is the data you need to fix the curriculum.

Last updated

What goes wrong today

Stuck is silent, and expensive

A student blocked on an environment error at step 3 can burn an hour before asking. You find out at the retro. A one-tap 'stuck' marker pinned to the exact step turns that hour into a minute.

You cannot be at thirty screens at once

Walking the room does not scale past about ten people, and it does not work at all remotely. A live grid does both, and it tells you where to walk first.

The curriculum bug hides in the aggregate

If half of every cohort marks step 7 stuck, that is not thirty students struggling — that is one badly written step. Per-step data across runs makes it obvious.

How a session runs

  1. The lab is a Markdown file

    Which means it lives in your curriculum repo like everything else. Fenced code blocks render properly, # headings split the steps, and a #[quiz] step drops in a knowledge check. Import the .md you already have.

  2. Let people roam

    Per-session configuration decides whether participants can look ahead, look back, or must stay on the host's step. For a lab, let them roam — fast students keep moving while you work the stuck queue.

  3. Work the help queue

    Raise-hand and help requests form a queue that is separate from chat, with an explicit resolve action, so requests do not scroll away. Inline annotations let a student attach a question to the exact line of the exercise that broke.

  4. Fix the step live

    When the instructions are wrong — a typo in a command, a missing flag — edit the step in place. Everyone's view updates without restarting the session. Insert a new step if a prerequisite turns out to be missing.

  5. Compare cohorts

    Each run produces its own report: timeline, engagement, quiz results, where people stalled. Export as Markdown and diff cohort over cohort.

What you get

  • Fenced code blocks and images render as first-class step content
  • Per-step stuck signals, queued and resolvable
  • Inline annotations anchored to the exact passage
  • Roaming enabled or disabled per session
  • Live step editing when the instructions turn out to be wrong
  • Markdown in, Markdown out — keeps the lab in your curriculum repo

Frequently asked questions

Does it run code or check submissions?

No. Workshopy runs the session, not the code — there is no sandbox, no test runner and no automatic grading of submitted work. Students work in their own environment; Workshopy tracks where they are and what is blocking them. Quizzes are the only auto-graded element.

Can I use it for remote cohorts?

Yes, and that is where the progress grid earns the most — remotely you have no room to read. Run it alongside Zoom or Meet; Workshopy is not a video tool and does not try to be.

How large can a cohort be?

200 participants per session on Pro, 30 on the free plan. Pro also allows 10 concurrent live sessions, which covers parallel tracks.

Can a TA help monitor the room?

Not yet — a session has a single host today, and a co-host or TA role is on the roadmap rather than shipped. A TA can join as a participant, but they will not see the host dashboard.

Also built for

Run your next workshop with the room visible.

Set up your first workshop in minutes — free, no credit card.