Most AI tutoring tools for kids work the same way: open a separate tab, describe your problem in words, hope the AI understands what you mean, then switch back to what you were doing and try to apply the advice.
For a 10-year-old trying to debug a Scratch project, that workflow falls apart almost immediately. They don't have the vocabulary to describe their block structure accurately. They can't copy-paste code — Scratch doesn't have text code to copy. And by the time they've switched tabs twice, they've lost the thread of what they were trying to fix.
Pengi takes a different approach. It's a Chrome extension that lives inside the Scratch editor — not in a separate tab, not as an external website, but as a panel that opens directly on scratch.mit.edu. When your child clicks the Pengi button, the AI already knows what's in the project: the sprites, the scripts, the variables, the event listeners. No description needed. No copy-pasting. No context-switching.
What "Real-Time" Actually Means
The phrase "real-time AI tutor" gets used loosely, so it's worth being specific about what Pengi does.
When your child opens a Scratch project with the Pengi extension installed, Pengi reads the current state of the project in the background — the block structure of every sprite, what variables exist and how they're scoped, which events are connected to which scripts. This happens continuously as they work.
So when they ask "why isn't my sprite moving?", Pengi isn't answering based on a general knowledge of Scratch. It's answering based on their project. It can see that their move block is outside the forever loop. It knows whether they have a "go to x/y" block running on a loop that's canceling out the motion. It sees the actual structure causing the actual problem.
This is the fundamental difference between a Scratch AI tutor Chrome extension that reads the project and a general-purpose chatbot that doesn't.
The Problems Kids Actually Hit on Scratch
After working with thousands of young Scratch users, the same categories of bugs come up again and again. These are the moments that end sessions early if there's no good help available:
The sprite that won't move. Almost always: the move block is outside the forever loop. One drag fixes it — but without understanding why the loop is needed, the same mistake reappears in the next project.
The game that crashes. Usually an infinite clone problem. A create clone of myself block inside a forever loop with no stop condition. Clone count grows until the browser can't keep up.
The score that doesn't update correctly. Scratch variable scoping — "for this sprite only" versus "for all sprites" — is one of the most counterintuitive concepts in the platform. The fix is a single dropdown change, but the concept behind it takes guidance to really land.
The blank canvas. "I want to make a platformer but I don't know where to start." Not a bug, but just as likely to end the session. Kids who can't break a big idea into small steps often freeze — or copy someone else's project and learn nothing.
In each of these cases, the right response isn't a solution handed over. It's a question: What do you think this block is doing? What happens if you put that inside the loop? If the variable is "for this sprite only," can the score sprite read it?
The Socratic Method, Applied to Scratch
Pengi uses the Socratic method as its core teaching approach. Instead of giving the fix, it asks the question that leads the child to find the fix themselves.
This matters more than it might seem. A child who receives an answer learns that specific answer. A child who finds the answer by thinking through a good question learns the underlying concept — and develops the debugging instinct that carries into every project they build after this one.
The session might look like this:
Child: My sprite keeps teleporting to the wrong place. Pengi: What block are you using to set the starting position? Where does it run in your script? Child: It's in the when-flag-clicked block… oh, but I also have a forever loop that moves it. Pengi: And which one do you think runs more often?
No answer was given. The child worked it out. That's the session that sticks.
Voice Interaction
Not every kid wants to type out a question. Pengi supports voice interaction alongside text, which makes it significantly more accessible for younger users — kids aged 7 or 8 who find typing slow, or who express themselves more clearly out loud than in writing.
A child can simply say: "My clone keeps making more clones and the game crashes." Pengi hears that, cross-references it against the project structure it's already read, and starts asking the right questions. The interaction feels less like using a tool and more like talking to a tutor who's looking at the same screen.
Why Chrome Extension Format Matters
The design decision to build Pengi as a Chrome extension rather than a standalone app is intentional.
Kids use Scratch on scratch.mit.edu. That's where their projects live, where they share work, where their class might be running assignments. An AI tutor that requires leaving that environment — opening a new app, logging into something else, uploading screenshots — creates friction that's especially damaging at the exact moment a child is frustrated and stuck.
The Pengi Scratch AI Tutor Chrome extension installs in about 30 seconds and then disappears into the browser toolbar until it's needed. When a child opens a Scratch project, a small button appears in the editor interface. When they need help, they click it. When they don't, it's invisible.
No new app to learn. No account on a separate platform. No workflow change for the parent.
Safe for Kids, Visible to Parents
Pengi is built specifically for K-12 students. The extension only responds to questions about the current Scratch project — it doesn't engage with off-topic conversations, doesn't have social features, and doesn't expose kids to content outside the context of coding help.
Parents can create managed student accounts, which means the child logs in with a student-specific login rather than an email address, and parents retain visibility into how the account is being used.
For schools and families who are cautious about AI tools, this structure matters. Pengi isn't a general-purpose AI given to a child — it's a focused tutoring tool with a narrow scope.
When to Use It
The highest-value use case for the Pengi Scratch AI Tutor Chrome extension is the evening session — the time when a child is practicing at home, between classes, and hits a wall that would otherwise end the session.
A good Scratch class gives kids a foundation. The hours they practice independently determine whether that foundation becomes real fluency. Pengi fills the gap that exists between the end of one lesson and the start of the next — available at 9pm, on weekends, during school holidays, whenever the child is coding.
If your child uses Scratch, the simplest way to see how it works is to install the extension and watch what happens the next time they get stuck. The first session usually answers the question.
