For whoever runs the session

Run it with your own group

{Length} over a video call, {building} of it building in breakout rooms of up to four. Written for people who don't code.

{length:number}{length:unit}, start to finish
{building:number}{building:unit} of building in breakout rooms
4people at most in each room, same level together
{parts}parts, each with a stage, a checklist, and messages

Present the stage Speaker notes Start with Before the day

Two ways to run it

Most hosts

From this site, as it is

No code. You make your own Google Meet and your own copies of two Google files (below), and paste their links in the chat; the pages tell people to look there.

How it works: The stage and the speaker notes work on any day: the stage moves when you press next, and its clock starts when you call the session to order.
What you give up: On a day other than the first run's, the participant pages show the kit, not a live schedule, so your chat says what's next.
What still shows the first run's: The partner credit on every page, the "first run as" line, and the invitation on Home before the day. Nothing in the parts, the messages, or the stage names a date, and the stage's last screen says only thank you; what your group does next, you say aloud.

Start with Before the day

With someone who knows GitHub

Your own copy of the site

Copy the kit, change one text file of dates, times, names, and links, and every page, the stage, and the notes follow your session, at your own web address. About an hour. The steps are in the README's "Run your own session."

The kit is free to reuse and adapt for non-commercial sessions under its license (at the foot of every page): keep the maker's credit, share your changes the same way, and replace the partner credit with your own host's name in your own copy.

Who you need

A presenter. Runs the stage, talks, and demos the three levels. That's probably you.
A co-host. Made a co-host in Meet beforehand (Host controls, then People).
- Before the rooms: watches the chat, lists the anchors, builds and opens the breakout rooms, and writes room numbers in the Breakout Planner.
- During: answers Ask for help, lines up Show & Cheer, and notes a build for each award.
- With more than about thirty people, a second co-host to visit rooms.
Anchors. Participants, not staff: anyone who rated themselves 4 or 5 or said what they'd built. One per room where one fits. The co-host tells each one, by private chat: "You're your room's anchor: share your screen first and start a starter together."

Before the day

Do all three levels yourself, from Three levels. Allow an hour. That page explains every word here: Canvas (Gemini's workspace beside the chat), embed, Apps Script, a folder's ID, the permission screen.
Set up the three demo tabs in one Chrome window:
1. Your AI chat with the Oracle starter pasted in and running. (The same Oracle is built into the stage's welcome screen; this is the same starter, shown a second way.)
2. Gemini with Canvas on, with the Charter Cards prompt and a made-up charter ready to paste, and a Google Site you can edit open beside it.
3. script.google.com with the Drive Inventory pasted in, a practice folder's ID in place, run once already so no permission screen appears live.
Participants then make the same three kinds of thing in their rooms: a tool in their chat, a page on a Site, a script in their Drive.
Make your own copies of two Google files. Start from the first run's, the Breakout Planner and the walls deck, then File, Make a copy, and clear the names. Share both so anyone with the link can edit; people from other districts will need it.
- The Breakout Planner: a Google Doc with a line at the top for the host's word to the rooms, an Ideas list, and a heading for each level with a table under it (Name, Partner, Room).
- The walls deck: a Google Slides deck of five slides: three empty ones for the gallery wall (people paste a picture and link it to their work; how, on Invent your own), one headed "I wonder", one "I worry".
Your Meet. Meet can't message every room at once, so hosts visit rooms.
- A week ahead: breakout rooms need a Google Workspace edition that includes them. Start a Meet, open Activities (the shapes icon at the lower right), and look for Breakout rooms.
- In Host controls (the shield icon): keep Share their screen on for everyone, so builders can present without being co-hosts, and make your co-host a co-host under People.
- On the day: the co-host sets the number of rooms in Breakout rooms, drags names in, and presses Open rooms; Meet numbers the rooms itself.
Check a staff account like your participants'. Paste a starter into Gemini with Canvas on and see the tool run beside the chat. Make a blank Google Site and paste an embed. Run the Drive Inventory and get past the permission screen. If one is off, ask your technology office now, or plan that level's fallback: ChatGPT or Claude for level 1; skip level 2 or 3 and send those people to level 1.

Send participants what they need a week before: a laptop or Chromebook, an AI chat they can sign in to, an idea, and made-up data only. The Start here section on Home says it in their words.

To: your group, a week before

You're invited to {title}: {length} over video to build small, useful tools with AI, no coding background needed, and leave with something worth showing a colleague. Bring a laptop or Chromebook, an AI chat you can sign in to (Gemini with your school Google account, ChatGPT, or Claude), and an idea: something small you'd want for your work. Everything is here: https://{url}
Made-up names and data only, every time.

Rehearse with the stage in one window and the speaker notes in another, and walk the session with ?now=10:50 on the end of any page's address to see it at that moment on the first run's day.

Materials

Open on the day

Present the stage Speaker notes The participant page

Your links

Your Google Meet
Your Breakout Planner
Your walls deck

If the site is blocked

The same session and the same starters as two slide decks, for when this site is blocked at a school, or if you'd rather present from slides: open one and choose File, then Make a copy.

Using the stage

Open the stage and the speaker notes as two windows of the same browser on the same computer; moving one moves the other. In Meet, share the stage's tab only (Present now, then A tab, with Also share tab audio on for the Oracle). For the three-level demo, switch to sharing the Chrome window that holds the three tabs, so the tab switches come through, then back to the stage's tab. Keep the notes off the shared screen.
The session clock sits large on the first screen until you press Call to order; then it counts the two hours down in the rail's corner. Timers are yours to stretch; nothing counts down to a clock time.
Stop sharing before a builder presents, and share the stage again after.

← →: Back and next screen
T: Start or pause a screen's timer (on the first screen, call to order)
+ −: A minute more or less on a timer
C: The session clock large, with wait-time buttons
N: Jump to the screen the clock says is on
S: Open the speaker notes
F: Full screen

Forming teams of four, by level

During Welcome ({welcome.length}), main room. In the chat, everyone rates how much they've built with AI, 1 to 5, and builders say what they made. The co-host lists the 4s, the 5s, and the builders: the anchors.
During Three levels ({levels.length}). The presenter shows the three levels live. Nobody is sorted; the levels are for choosing.
During Show & Tell ({show.length}). The co-host pastes the Breakout Planner's link in the chat. Everyone adds their name under the level they want to try, with a partner's name beside it if they have one. The co-host opens Breakout rooms and makes rooms of up to four from each level's list, partners together, an anchor in each room where one fits, then writes the room numbers in the Room column and messages each anchor.
When the Remix Arcade starts. Open the rooms. Everyone finds their room number next to their name. Level 1 rooms start with a starter; level 2 and 3 rooms start with their level's example on Three levels.
Latecomers. Ask which level, add them to that level's smallest room, and write the room number next to their name.

How many rooms?

People on one level's list (run it once per level)

Run of show

The {parts} parts run end to end, {length} in all; the breakout rooms run without a break through the Remix Arcade and Invent your own, {building}.

Each part: what's on the stage (each screen opens the stage there), a checklist for hosts, and messages ready to paste.
Where a message has a blank like "(your planner link)", paste your own link over it after copying.
Checklist ticks are saved in this browser only. On the first run's day the part the clock says is on opens by itself; any other day, open the part you're in.

In the rooms, and after

In the rooms

The anchor shares their screen for the first {buildAlong}. Everyone builds along, then builds their own.
Breakout chats start empty: paste the page link when you visit a room.
People press Ask for help in Meet to call a host; the co-host watches for it.
Meet can't message every room at once. At the switch from the Remix Arcade to Invent your own, the co-host visits each room to say "switch to inventing your own: your own idea, or one from the Planner," and changes the Planner's top line, which everyone has open. With {nudge} left, around again: pin something to the gallery wall, even half-built (how, on Invent your own). At zero, the co-host closes the rooms; Meet gives everyone a short countdown.

Safe play

Made-up names and made-up data only. Nothing about real students goes into an AI, and initials or ID numbers don't make data anonymous.
Names typed into a tool running on this site stay on that computer. Names pasted into an AI chat go to that company.
Anything published or shared from Claude or Gemini as a link can be opened by anyone with that link. Share inside your district's settings, and never with real information in the tool.
Before anyone shares a tool beyond their team, check it: can you use it with Tab and Enter alone? Is the text easy to read on its background? Does every button and box say what it is? (How to check.)

The sources behind these: student data, security, and accessibility. For leaders: a five-source reading path.

Show & Cheer and after

Builders share with Present now, then A tab, so their tab's sound comes through. About three minutes each; reset the stage timer between builders.
If sharing fails, share the gallery wall and click their picture to open what they made.
The three awards are on the stage: Most Delightfully Broken, Best Rescue, Most Likely to Actually Get Used. The co-host notes one build for each while visiting rooms, and the presenter reads them out. For fun, not ranking.
People keep their own work. Nobody collects it.
The follow-up points to this site, its Sources page, and whatever your group does next.

When it breaks

Canvas missing in Gemini: Level 1 works in ChatGPT or Claude; say so in the chat.
Apps Script blocked: Level 3 becomes a demo you show, not a thing they run; send those people to level 1 or 2.
An AI refuses or errors: Start a new chat and paste again; that counts.
A room with no anchor: They open a starter together and press Play; the co-host visits first.
One person alone in a room: Merge them into the smallest room at their level.
No breakout rooms on your Workspace edition: Everyone builds in the main room with mics off, and the chat is the room.
Running long: The stage timers are yours; shorten Show & Cheer before you shorten the building.
Site blocked at a school: The two slide decks in Materials hold the same session and starters.

How the first run went

What people asked, showed, and offered that morning, and how it went against the plan: From the room.