Why I Built Hi, Bot Code

When I went looking for a coding environment to use with students in Hi, Bot, I kept hitting the same wall.

Every tool either required an account, required an install, required IT approval to unblock something, or had third-party analytics embedded so deep you couldn't audit what was being collected about a thirteen-year-old's session data. None of that is acceptable when the thing you're trying to teach is that the browser is already a development environment.

Hi, Bot Code is a single HTML file.

No build step. No login. No tracking. You open it and you're coding. There's a visual editor and a code editor and they stay in sync. You can see your webpage render in real time in a sandboxed iframe. When you want to export, you get formatted code that drops directly into CodePen, Replit, Carrd, or Webflow—whatever the student wants to take it to next.

The architecture is part of the lesson. Every student can see that the tool they're using is itself a web page. The source is readable. A curious student can open the inspector, look at how the editor works, and start understanding what they're building toward. The tool doesn't pretend to be magic. It shows its work.

Five progressive challenges, six achievement badges, twelve page templates. These are scaffolding, not requirements. The real measure of success is whether a kid leaves a session with a URL they built themselves—not simulated inside a sandbox, but hosted somewhere real, that someone else can visit.

I wanted the tool to have no excuse for not working. No account to create. No internet required after the first load. No teacher permissions needed. You hand a student a browser and they can start.

code.hibot.space. Free. No account.