← Demo plan · Showcase · JourneyDocumentation · Try the demo
Game Track · Try the demo · opened 20 Sep 2026 · for the Academy and Studios team

Play around with it

The demonstrator is open to the team. Be a student: install the Workbench, make Pong with the two AI desks, publish it. Be a lecturer: watch the prompts arrive and play the games. It is a two-week build in its first days, so expect rough edges; tell Neo what breaks. Demonstrator, not the kit.

No install needed to try the box: course.neotodak.com/demo runs the one box on a shared demo machine, with the game in a viewer. The steps below are for the full Workbench on your own PC.

You will get from Neo
  1. Team PINSix digits. Opens the lecturer page course.neotodak.com/journey.
  2. Two filesworkbench.env (the recording token) and showcase-deploy-key (lets your machine publish to the team showcase). Keep them private; they are demo keys and can be revoked at any time.
  3. Your own AI loginsClaude Code needs a paid Claude plan; Codex needs a ChatGPT plan. If you only have one of them, use that desk for everything: both read the same instructions.
01

As a student

About 20 minutes the first time, mostly downloads. Mac, Windows or Linux. You need Node 18 or newer and VS Code with its code command.

  1. Get the kit. git clone https://github.com/broneotodak/todak-game-kit.git (ask Neo for access; it is private for now).
  2. Install the Workbench. Put the two files from Neo somewhere, then run the installer. Mac or Linux: TGK_INGEST_TOKEN=$(grep TGK_INGEST_TOKEN workbench.env | cut -d= -f2 | tr -d '"') TGK_PUBLISH_KEY_FILE=./showcase-deploy-key bash todak-game-kit/workbench/install/install.sh. Windows PowerShell: set $env:TGK_INGEST_TOKEN and $env:TGK_PUBLISH_KEY_FILE, then powershell -ExecutionPolicy Bypass -File todak-game-kit\workbench\install\install.ps1. It installs the three editor extensions and the Todak sidebar, downloads Godot 4.7.2 with its web export files (about 1 GB, once), and writes your environment. Open a new terminal afterwards.
  3. Import the profile once. VS Code → Profiles → Import Profile → todak-game-kit/workbench/profile/todak-workbench.code-profile.json. Sign in to the Claude Code panel and the Codex panel with your own accounts.
  4. Make a game. tgk new pong my-pong --student yourname --week 3, then code my-pong. The Todak sidebar shows Week 3 · Pong and four steps.
  5. Play it first. Press Run in the sidebar (or tgk run). The right paddle plays by itself; yours does not move yet. That is step 2.
  6. The one box. At the top of the Todak sidebar there is a Desk: type what you want in plain words. Artwork requests go to Astra, code requests to Claude Code, and the reply says which desk answered and why, with a link to send it to the other desk instead. "Build me the whole game" gets the step list. After a code change, the box asks you what changed; one sentence unlocks the next step. (Sidebar 0.2.0 or newer; re-run the installer if you installed earlier.)
  7. If you prefer the raw panels: open the Codex panel and ask Astra for paddles, a ball and a title in a style you like. Pictures land in design/ and show on the design board. From a terminal: tgk ask "paddles, a ball and a title screen, pixel style".
  8. Or the raw Claude Code panel: type: make the left paddle move with W and S (or from a terminal: tgk ask "make the left paddle move with W and S"; afterwards the desk asks you to explain the change in one sentence: tgk ask --explain "..."). Watch scripts/paddle.gd change, then Run and press W and S. Then: make the ball launch and bounce off the top, the bottom and the paddles.
  9. Review. Press Review. Read the report. Fix what it says, review again.
  10. Publish. Press Publish (or tgk publish web). In about a minute your game is on the team showcase and in the course showcase, with your name on it.
  11. Look at your own journey. Press "Open journey" in the sidebar, or tgk journey. Every prompt you typed in either desk is there. The lecturer sees the same on the web.

Rules of the game while you play. Do not paste real student or company data into prompts; this is a demo store. Prompts are recorded on purpose. Keep the two AI desks to their lanes if you can (Astra designs, Claude Code builds), and notice how it feels when you break that rule.

02

As a lecturer

  1. The trainer's box. course.neotodak.com/trainer, no PIN for the demo. Left: the first-lab presentation. Right: every student in the demo room with ticks for today's objective. Below: ask "who hasn't finished the paddle", "who is stuck", "show Ali", "review Ali", or "note Ali: …" and the note appears in Ali's box. Projector view hides the box and enlarges the board.
  2. The Prompt Journey. course.neotodak.com/journey, enter the team PIN. Filter by student. Each row is a prompt (with its desk), a review score, or a publish link. New prompts appear within seconds of being typed on a connected machine.
  3. The showcase. course.neotodak.com/play lists every published game; the ones marked "team" come from the team showcase. Play them on a laptop or in landscape on a phone.
  4. Try the walkthrough test. Ask a "student" to explain their paddle code with both panels closed. That is the assessment idea in one minute.
  5. What to tell Neo. Where a beginner would get stuck, what the sidebar should say differently, what the review missed, and how long the install took on your machine.
03

Known rough edges