← All AI Engineer talks

AI Engineer Summit 2025

Tools for the Next Generation of AI Engineers

Stefania Druga· Research Scientist, Gemini, Google21:47

Read the talk

Building AI tools children can understand, question, and change

From a robot playing hide-and-seek to a Scratch coding companion, Cognimates makes AI literacy a matter of building, testing, and retaining control over a project.

From a talk by Stefania Druga

Before you start: No machine-learning background is required; familiarity with conditions, loops, and the idea of training a model from examples will help.

What if children built the AI tools they use?

Students already use generative AI for homework. What would it take for them to become designers of those tools, rather than only recipients of answers? Stefania Druga opens with that question of participation. Multimodal AI could expand what children make and how they learn; she also describes cases in which students prefer AI assistance to human tutors. Her goal is to put children inside the engineering process.

Druga cites Gen Z as 70% of AI users, but that denominator should not be carried forward as an established fact. The related Salesforce survey measures the reverse: 70% of surveyed Gen Z respondents reported using generative AI. The practical design question remains how to turn young people's use of AI into an opportunity to understand and shape it.

Scratch provides a starting point: free, open-source visual programming developed at MIT, where programs are assembled from blocks. Druga describes its worldwide reach as more than 100 million children. During her master's work in the MIT lab, she began Cognimates in 2015 to extend that accessible programming environment into AI.

0:400:54
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:40 · section reference included

A robot, a person detector, and a missing loop

Cognimates extends Scratch so children can build games, train AI models, and program hardware with the same Lego-like blocks. One early example comes from Tiana, who was nine when she wrote her first robot program and then played with it for half an hour. Her game was hide-and-seek: she ran around the room while the robot turned and, whenever its detected-person count exceeded zero, said “I see you.”

Children gathered around a robot beside blocks that turn attention on and say “I see you” when the number of people exceeds zero.
A Cognimates project pairs robot play with a short visual program.

The interesting bug is visible without understanding the person detector's internals. The program checks the condition only once. To keep playing, it needs a loop around the detection and response. Expressed as Scratch blocks, that repeated behavior is:

scratch

when green flag clicked
forever
  if <(number of people) > (0)> then
    say [I see you]
  end
end

An AI capability becomes something a child can reason about through ordinary control flow. The detector supplies a value; the child's program decides what to do with it and whether to keep checking. Scratch's block library, coding area, and stage make that connection quick enough to discover through play.

1:542:12
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

1:54 · section reference included

Taking AI apart through play

In an embedded video, a child describes playing rock-paper-scissors through a camera: make a hand gesture on cue, then compare it with the computer's move. The child explains the computer's improvement through an analogy with practice—people do not know everything at first either, but get better by trying. The project gives the learner a concrete behavior to observe and discuss.

Visual blocks take a webcam photo, ask what is in it, switch to a scissors costume, and ask “Did I guess right?” Hand gestures appear on the stage.
A webcam-based rock-paper-scissors project in Cognimates.

The adults describe different starting attitudes. Technically confident parents readily encouraged participation; another parent and teacher acknowledges that AI can feel frightening while still treating understanding it as an essential skill. A child's analogy makes the educational purpose especially clear: their father once took a car apart to see how it worked. Programming systems that adults usually build offers a similar way to inspect technology from the inside.

3:093:18
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

3:09 · section reference included

A low-confidence narwhal becomes a data question

The projects from 2015–2016 used basic image and text classifiers. Alongside custom training, Cognimates supplied extensions for sentiment analysis, image classification, voice assistants, micro:bits, and robots. Children who found voice assistants too limited could program them to remember personal details and preferences. On the training page, they could drag and drop image examples to build their own classifier.

One child wanted a unicorn-versus-narwhal game. After collecting training images, the learner could select that custom model in a program, hold a drawing up to the camera, and inspect both the predicted class and its confidence. A narwhal prediction with very low confidence creates a useful next question: what differs between this drawing and the examples used for training? In Druga's example, most training images were cartoons, so the learner's next move was to add more hand-drawn examples. The important feedback is not merely whether the label is right; it is the connection between the model's behavior and the data the child supplied.

That cycle—supply examples, inspect a prediction, revise the examples—makes AI and data literacy tangible. The same tools supported projects across subjects:

  • Science: turn a webcam into a microscope to examine food.
  • Games: build camera-based rock-paper-scissors.
  • Literature: analyze speech for resemblance to a writer's style or another category of language.

Across public schools, private schools, and community centers, Druga observed children forming hypotheses about models and robots, testing them, and revising their understanding. The design requirement is to make that scientific process easy to enter, with projects engaging enough that children want to continue.

To examine whether making changed children's perceptions, Druga asked questions before and after their programming and model-training experience. Were voice assistants, smart toys, and robots intelligent? Trustworthy? Likable? Friendly? This work preceded ChatGPT and Gemini. Druga reports a significant change in intelligence attribution after children learned to train and program models, although she supplies no effect size or statistical details here. She also reports that Cognimates was used worldwide and translated into 50 languages.

4:334:46
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

4:33 · section reference included

Designing a companion before building one

When the pandemic left families learning at home, the design problem expanded from children's individual projects to parents and children coding together. An early robot tutor illustrates the interaction Druga wanted to preserve. Jibo asks the learner to write a program that lets it learn their name: first find the green-flag block, then find the ask block. The robot offers feedback as the learner works. The object being programmed participates in a conversation about its own program.

A robot is an expensive prerequisite, so Druga moved toward a browser-based pair-programming companion. Before implementing an assistant, she ran design studies with families from varied backgrounds across ten US states. In this Wizard of Oz study, Druga herself supplied the apparent AI's chat responses. Children initially interacted as though they were talking to an assistant and were told afterward that a person had been responding. This let the study investigate what support families wanted before committing to a system design.

Children wanted help generating ideas, not an assistant that completed the project for them. A bear game or an interest in soccer could become the starting point for brainstorming. One twelve-year-old described the difficulty of beginning a project and immediately running out of ideas. Once a project existed, questions could help elaborate it: in Pong, how should the ball move, and how could it move faster? These prompts give the learner something to decide and try.

Encouragement mattered too. Participants described the frustration of getting code to work and the satisfaction of having someone acknowledge success. Parents reported that participating children spent twice their usual time programming. That comparison came from parents' accounts, not an instrumented measurement of programming time.

The companion did not remove the need for an adult. Parents still helped when the interaction became distracting or failed to manage turns between siblings. More complex Scratch concepts also proved difficult to explain: clone creates additional instances of an object, while broadcast introduces communication between scripts. Those limits helped define what the implemented assistant would need to support and what its evaluation should test.

8:098:19
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:09 · section reference included

From support tasks to Cognimates Copilot

Druga next assembled an evaluation benchmark, describing more than 100 Scratch program cases used to compare models. The tasks followed the needs identified in the family study: explain code, explain it through learning exercises, debug it, and generate ideas. She calls the results promising but gives no scores in the talk. The benchmark is a test of assistance on these tasks, not a measurement of children's learning gains.

The next step was to build Cognimates Copilot and test it with young people. Druga reports a newly completed study involving 18 participants from 11 countries, working in different languages. The implementation is straightforward: a code editor sits beside an AI chat; messages go to a web server, which returns responses from AI services. She was evaluating several models, including one fine-tuned on Scratch projects. The system could also generate images for games.

Architecture diagram groups Code Editor and AI Chat, Send Msg and Response, and AI services labeled LLM Support and Generate Art.
Cognimates Copilot connects a code editor and AI chat to a web server and AI services.

A session with a child from Mexico took place entirely in Spanish. Across the sessions, Druga observed conceptual support, design support, positive encouragement, and help navigating the platform. She also observed failures and occasions when children declined the assistant's suggestions. Those refusals matter: useful assistance includes leaving room for the learner to disagree.

12:1412:30
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

12:14 · section reference included

Helping without taking over

A student from Jamaica who had never programmed in Scratch reached a functional program with Copilot's support. Much of the help was practical orientation: where to find a loop block and how to create variables. For experienced users, support shifted toward assets, code improvements, additional features, and new levels.

Learner needUseful assistance
First projectLocate blocks and create variables
Existing programSuggest improvements and features
More elaborate gameGenerate assets and propose levels

The same chat interface can serve these different needs, but the substance of its help must change with the learner's experience.

Children also used the assistant for backgrounds, character names, and plot ideas. In one example, a student pasted an image of their code, requested an idea, and then rejected the proposed movement. The assistant replied, “No worries. It's your game. Have fun.” The child remains the author, including when they reject the tool's advice.

That principle shapes how help is offered. Druga describes the prototype's default as asking questions instead of giving an answer. If a stuck student asks the same question three times, it offers a hint. This balances support with the challenge that makes the programming activity educational. It also treats the assistant as a motivator and starting point for Scratch's cold-start problem: arriving at the editor without knowing what to make.

Customization is part of that balance. Some children wanted voice interaction; others wanted only typing. Some always wanted three ideas; others preferred one. A fixed response style would make the same assistant helpful to one learner and intrusive to another.

13:5514:07
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

13:55 · section reference included

Moving assistance into the programming environment

Participants wanted assistance beyond a chat sidebar. They asked for agents that could move blocks alongside them and demonstrate programming: watch an agent build Pac-Man, or watch five agents collaborate on an Asteroid game. They also wanted generated assets placed directly on the stage instead of delivered only through chat. These were requests for future behavior, not capabilities demonstrated in the study.

Druga's proposed next phase was to integrate the agent throughout the interface, add sound generation, and potentially let it react to a camera stream. As capabilities expand, the assistant also needs to explain its limits. She gives examples of explanations referring to unavailable training images or a prompt that restricts answers to Scratch. The design requirement is understandable disclosure of the actual constraint; those illustrative messages do not establish why a particular model failed. She then turns to a live demonstration of the prototype.

16:2116:39
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

16:21 · section reference included

From racing-game ideas to handwritten digits

The live session starts with a greeting. Copilot asks what the learner wants to work on in Scratch, and an audience suggestion supplies the project: a racing game. Asking for ideas produces a turbo-boost button and extra speed. This demonstrates the first step out of the blank editor—a specific feature that a learner can accept, change, or ignore.

Druga then moves from ideation to an existing Scratch project. She points to OCR implementations as examples of the sophisticated programs people build in Scratch. Browsing is slow, so she loads a project she has already downloaded. She draws input on its stage and asks the project to recognize it, describing the results as two and eight. The recognition belongs to the loaded Scratch program; the adjacent chat is there to help the learner understand and work with the project.

Cognimates editor with stacked programming blocks, a purple handwritten mark on a white grid, visible 2 and 8 digits, and an AI chat sidebar.
The digit-recognition demo shows a purple handwritten mark alongside the project's code and chat.

For a complex program, the intended explanation workflow is:

  1. Capture a screenshot of the relevant blocks.
  2. Attach that image to the chat.
  3. Ask the assistant to explain the code.

The two-screen setup prevents Druga from capturing the intended screenshot during the live demonstration. She stops the attempt without showing an attachment or a resulting explanation. The digit-recognition interaction is visible; the screenshot-to-explanation sequence remains incomplete onstage.

18:0518:17
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

18:05 · section reference included

Starting AI literacy early

Druga closes by describing the project as free and open source, inviting contributions, feedback, and sharing with young people as more features arrive. The invitation extends the same participatory model used in the studies: the people who use these tools should help determine what they become.

She also invokes the EU AI Act as a reason AI literacy can no longer be treated as optional. In her account, a requirement had passed earlier that month and called on providers and deployers to support sufficient literacy among staff and product users. Her educational conclusion is to begin that work early, while children are learning how to investigate and build with AI.

Her final pointer is to papers and studies on her website covering AI literacy, AI education, mathematical misconceptions, and science. The work connects those subjects through a practical learning experience: children make something, encounter a surprising result, and gain enough understanding to decide what to try next.

20:2520:35
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

20:25 · section reference included

Resources

From the talk

  • AI FriendsPaper

    A three-week family study of a researcher-operated coding companion, examining ideation, parental support and children's creative agency.

  • An evaluation of model assistance for understanding Scratch code, debugging and generating project ideas.

  • Survey findings on generative AI adoption across generations in four countries.

Updates since the talk

Read the complete timestamped transcript
  1. 0:00

    [on hold music] Thank you so much.

  2. 0:18

    Hello, New York. Uh, how are you doing?

  3. 0:22

    Good. [laughs] Okay, so I know you've been hearing a lot of amazing talks, and before I get started, I wanted to see a quick show of hands. How many of you are here for the first time at AI Engineering Conference?

  4. 0:35

    Wow, that's amazing. How many of you are international, outside of US?

  5. 0:40

    Incredible. Thank you for coming. Um, so today I'm gonna talk about how do we open up this conference and how do we open up this knowledge to the next generation of AI engineers, which are young and, uh, well, much, uh...

  6. 0:54

    start much earlier. And why does that matter? It's because 70% of AI users are actually from Gen Z. Um, and we've seen the potential of multi- multimodal AI to transform education.

  7. 1:07

    We know that students are using generative AI tools for their homework, and I think they can use it in a much more interesting way. We also know that in many cases, they prefer it, um, to, uh, human tutors.

  8. 1:20

    And I want kids to actually be part of the engineers and the designers that create the tools for them to use. Um, and I turned to Scratch. I don't know, how many of you know Scratch?

  9. 1:35

    Wow. Uh, there are over 100 million children using Scratch worldwide. Scratch is a pr- a platform, it's free, it's open source, for coding for kids, it's visual programming. It was d- developed at MIT, and I was part of that lab and, um, during my master's, and that's in 2015 when I start working on Cognimates.

  10. 1:54

    Cognimates expands Scratch to actually allow children to learn about AI by building games, training their own, uh, AI models, and programming hardware as well. So it has these kind of blocks, they look like Lego blocks, and they can put them together in order to create their programs.

  11. 2:12

    Does anyone want to guess what this program do?

  12. 2:17

    Any guesses? So Tiana here, who was [REDACTED:age] at the time, she, she wrote this program for the first time and then played with the robot, um, using the program for half an hour, which was super fun.

  13. 2:31

    So it's a hide-and-seek game, right? So she would, like, run around the room, and the robot would turn around and say-- Every time it would detect a person, the number of people was, like, higher than zero, it would say, "I see you."

  14. 2:42

    There is a pro- a problem with the program, though. Can you spot it?

  15. 2:47

    How many times are we gonna play if we have it like this? Yeah. One. Yeah, so what do we need, Nick? Uh, we need a loop. We need a loop.

  16. 2:56

    Exactly. Awesome. Um, so the time to fun and the time to play, um, is very short in Scratch, which is why I used it when I built Cognimates. It has this library of blocks, a coding area, and a stage.

  17. 3:09

    And I'm gonna show you a quick video of how kids use it in order to learn more about AI. [upbeat music]

  18. 3:18

    So we were programming robots. You could play rock, paper, scissors.

  19. 3:26

    You did rock, paper, scissors into the camera, and on cue, you did one of the motions, and the camera did one of the motions, and it's like rock, paper, scissors, shoot.

  20. 3:40

    The computer gets, like, better as you play the game. 'Cause like us, we might not know everything at first, but if we keep trying, we get better.

  21. 3:50

    Everyone has heard about, like, machine-based learning or artificial intelligence, and there was a sort of no questions asked for a lot of the more tech-savvy parents. It was like, "Go for it."

  22. 3:59

    Technology is gonna be a huge part of their lives, much more so than my life. If it's scary for some people, this AI technology, I totally get it. But as a parent and as a teacher, I thought it was really important because these are skills that twenty-first century kids need to have.

  23. 4:14

    When my dad was young, he bought a car and took it apart to see how it worked. So you teach people that young how these things that grown-ups mostly program, how it works.

  24. 4:33

    So we did this in 2015, 2016. Uh, these AI engineers started very early. And at the time, they were training these custom models with basic classification models for images and text.

  25. 4:46

    Um, but they also had access to the entire library of extensions that we built for them, so they could use off-the-shelf sentiment analysis, image classification. They could program their voice assistants because they realized voice assistants were really limited.

  26. 5:00

    So they could program the voice assistants to remember things about them and their preferences, um, program micro bits, robots. And this is what the training page looks like. Um, they can drag and drop examples of images.

  27. 5:12

    So for example, one kid wanted to, um, make a game about unicorns and narwhals. So this was, like, what his training data looked like. And then this is what the program looked like.

  28. 5:23

    So he can choose his custom model, unic- unicorns versus narwhals, and then show different drawings into the camera and see what the model predicts. And moreover, it als- he also or she can see-- they can see the level of confidence of the prediction, which really helps them understand, "Oh, yes, this-- in this case, it guessed that my

  29. 5:44

    drawing was a narwhal, but the confidence level is very, very low. What do I need to do? I'm gonna go back to the-- my training and add more examples of images that are hand-drawn because most of my images are cartoons."

  30. 5:56

    So it really creates this AI li- literacy, data literacy, and demystifies everything that kids, uh, learn about AI or hear about AI. That it's evil, Terminator, or all sorts of things, right?

  31. 6:06

    Um, and- They built projects that went across different domains. So it was a project where they could look at things in their food by transforming a webcam into a microscope.

  32. 6:17

    They could build games like the rock, paper, scissors that you've seen in the video, or a literature program, uh, where you speak and it analyzes what you say and s-- uh, it's seeing if it's in the style of a s- famous writer or, uh, different other, uh, types of styles.

  33. 6:32

    And what's important, like, I tested this with kids in public, private, uh, s- uh, schools, and community centers, and what I found is that kids are actually like little scientists.

  34. 6:45

    So if we give them the right tools, they engage in the scientific process. They formulate hypothesis about how the model works or how the robot works, and then they test those hypothesis, and they refine their understanding in the process.

  35. 6:59

    And it's the same with the model training. So we need to create tools that enable them to engage in the scientific process as fast as possible, and create tools that are fun and sticky that they want to use.

  36. 7:13

    And why does this matter? Um, before, uh, allowing them to program with Cognimates and train their own models, I actually asked them questions about voice assistants and other, uh, smart toys and smart, uh, robots at the time.

  37. 7:27

    And I asked them, "Do you think it's smart? Do you trust it? Um, do you like it? Is it friendly?" And I asked the same questions about those technologies, we didn't have ChatGPT at the time or Gemini, um, at the end of the study.

  38. 7:40

    And what I found was that there was a significant difference in the intelligence attribution after they engage in this process of learning how to train a model, learning how to program it, understanding why the data matters.

  39. 7:53

    Um, so it does make a difference in demystifying the intelligence that we talk about. And this platform is used around the world. It's actually translated in fifty languages. And I realized after I worked on this, that it's not just the kids.

  40. 8:09

    Like, the pandemic came, and a lot of young people were stuck at home, um, so I had to, like, really think about how do I create and how do I work with families.

  41. 8:19

    So started to do, uh, a lot of other experiments. And I figured, like, what are the type of tutors or, uh, games or, um, platforms that families could use when they're at home and maybe they wanna learn how to code with their kids?

  42. 8:35

    And I'll show you an early prototype.

  43. 8:38

    Hi there. I would like to know your name, so let's do a program that allow me to learn it. Let's start with the green flag block.

  44. 8:46

    There you go. You did it. Now I need you to help me ask a question. For that, we'll need the ask block. See if you can find it. [pop]

  45. 9:02

    Awesome.

  46. 9:04

    So in this case, they're learning how to program a robot. It was a Jibo robot, and the robot itself, it's participating in the process. So you're having, like, this reflective, uh, conversation with the thing that you're programming, which is pretty cool.

  47. 9:18

    Uh, and we could do that much more than that now. Um, but because not everyone can afford to buy a robot or, like, it's not, you know, a required thing, I wanted to build something similar, like a pair companion for co- programming that works in the browser.

  48. 9:33

    So during the pandemic, I start doing these design studies with families in ten different states, uh, in US. Very different backgrounds, very different ethnicities. And this is very important, and I wanted to highlight that here.

  49. 9:47

    Before building the system, I mocked the system. So we didn't have a functional copilot or a functional assistant. I was the AI, um, and it was a Wizard of Oz study.

  50. 10:00

    Like, I, we were mo-- The kids did not know initially, we told them afterwards, that they're interacting with a person that... But they would interact via chat, and I really wanted to understand, what is it that they want?

  51. 10:12

    What kind of supports do they need from a pair programmer when they code on Scratch with their parents? And what I found was that they really wanna generate coding ideas.

  52. 10:22

    They don't want the copilot, uh, in Scratch or in Cognimates to do everything for them. They wanna kind of brainstorm, like, "Oh, uh, what if I wanna do a game about bears?"

  53. 10:32

    Or, "What if I-- I'm into soccer, like, give me some ideas." Um, that was a really big one. And here are some quotes. Like, uh, one of our participants who's twelve said, "Most people would like coding with AI friends because one of the hardest parts of our project is when you start and you run into a wall.

  54. 10:50

    You are out of ideas." So it really helped with the ideation process. It also helped them kind of express and elaborate their ideas. Like, if they would play a, a Pong game, it would ask like, "Okay, so how do we make the ball move?"

  55. 11:04

    Or like, "How do you make it move faster?" Um, so it was very helpful in that regard as well. And it supported their creative coding identity, right? So another quote, "I like it because sometimes when you code, it gets frustrating.

  56. 11:17

    When you finally get it to work, it's so good that it lets you feel good. It's good when you have someone that says to you, 'Good job.'" And what's interesting is that the kids participating in these studies spent double the amount of time programming that they would spend normally, and I, I got that from parents.

  57. 11:36

    And didn't always work. Sometimes, like, uh, uh, the parents were needed in the loop, like if it was too distracting or if it wasn't able to moderate turn-taking between siblings.

  58. 11:47

    Uh, or if the [laughs] yeah, you know, uh, agents have limitations, AI has limitations. Or it wasn't always able to explain the most complex concepts, like the, uh, in Scratch, there is this thing called clone when you create multiple instances of the same object or broadcast.

  59. 12:02

    That was harder to explain. So after doing this first design study and identifying, like, what are the core features that kids and parents want, um, I created a, a evaluation benchmark.

  60. 12:14

    So I actually had over a hundred cases of Scratch programs And I would run this against, like, different state-of-the-art models and see how good these models are at explaining the Scratch code, at explaining it with learning exercises, at debugging it, at c- generating ideas.

  61. 12:30

    And the results were very promising. So, um, the next thing was to build it. And this is, uh, the first time I'm showing these results. I just finished running the study, so it's very o- off the press, uh, very fresh, uh, from the, from the oven.

  62. 12:45

    And, um, uh, I, I just tested this Cognimates Copilot with young people, um, 18 young people from 11 different countries in different languages. And it was, it was kind of cool.

  63. 12:58

    Like, it's very simple. It's the code editor, and it has this AI chat. Um, it's sending a message to a web server and then gets a response. I'm, I'm using and evaluating different models, including a fine-tuned model on Scratch projects, and it can also generate assets, art, like images for their games.

  64. 13:16

    And here's an example from a session with a kid from Mexico. So all the session, like, was done in Spanish. I speak many languages, so I could do the session in different languages, and so does the copilot.

  65. 13:28

    Um, and what I found in analyzing these sessions, uh, from il- 18 kids is that the copilot provided all sorts of supports. And it was conceptual support, design support, positive encouragement, platform nav- navigation.

  66. 13:45

    There were instances where it failed. Um, and I also saw lots of instances where the kids would refuse the suggested help or the suggested ideas.

  67. 13:55

    And here's an example of code support. This was a student from Jamaica, and he had never programmed in Scratch before. So he was able to go from zero to actually having a fully functional program with the support of the copilot.

  68. 14:07

    And the co- the copilot was actually very helpful, not only in giving him ideas, but also helping him understand how to navigate the platform for a very, for the very first time.

  69. 14:16

    Like, "This is where you find the loop, uh, block, and this is where... how you create variables," or... Um, so it was very helpful for people who are new.

  70. 14:27

    For people who are advanced, it was also very helpful because it would generate assets that they really liked. Um, it would give them ideas, like, for how to refactor.

  71. 14:37

    It didn't call it refactor, but, like, improve the code, um, or how to add new features or new levels. And it was interesting because kids would use it in a lot of ways I didn't predict.

  72. 14:47

    Like, besides, like, generating the, the background in this game, also, like, for they wanted to get names, ideas for names for characters and ideas for plots. Um, and this is a great example, like, where a student is actually pasting, uh, an image of the code, and he's asking for an idea, and he actually doesn't like the answer.

  73. 15:08

    So he said, like, "I don't wanna do that type of movement." And then the copilot says, "No worries. It's your game. Have fun." [laughs] Right? So we wanna have tools that are actually prioritizing and encouraging young people's agency in this process.

  74. 15:23

    Some lessons learned. Uh, uh, to prioritize user's agency, to balance the support and the challenge that we give them. By default, the copilot does not give the answer. Initially, it ask, asks questions, and if the student is really stuck after asking the same question three times, it would give a hint.

  75. 15:45

    Um, to see these agents as motivators and starting point, right? Like, the effect of the blank page when you start to write. The effect i- in, in Scratch is called cold start.

  76. 15:56

    We see a lot of students that go to the platform, and they really don't know where to start. So it's very helpful for that too. And we learned that it was important to allow for flexibility and customization.

  77. 16:08

    I had kids that really wanted to use voice and other kids that did not wanna use voice. They just wanted to type, right? I had kids that said, "I always want it to give me three ideas," and other kids that was like, "No, just one idea is good."

  78. 16:21

    Um, so everyone wanted different things. And design agents that support, um, creativity is key too. So a lot of the participants told me they want the agent to be able to go and move the blocks with them, and they wanna have, like, see simulations of agents programming.

  79. 16:39

    Like, "How would an agent build a Pac-Man game? I wanna see, like, how five agents would collaborate to build this Asteroid game." Um, or, "I want when it generates the assets, instead of giving it to me in the chat, like, to have it directly on the stage."

  80. 16:53

    So the next, the next phase in prota- of the, of the prototype is to actually hack the OS entirely and integrate the, the agent at all different stages, uh, of the UI.

  81. 17:05

    And then support multimodal AI capabilities, like, including, like, sound generation and maybe reaction to camera stream. Um, and then the, the part that I... was very important is when it doesn't work or it cannot do what they ask of it to do, um, it should tell them why, right?

  82. 17:22

    Like, it should be like, "Okay, I cannot generate this type of images because my training set does not include it," or, "I can only give you answers about Scratch because that's what my prompt is," or, um...

  83. 17:34

    So it should be really transparent, uh, and explain its limitation in order to set the right expectations. So I'm gonna show you a quick demo. Let's see if it works.

  84. 17:48

    And this is just a prototype. And I learned that I'm giving this talk two hours ago, so please be kind. Um, so-

  85. 17:58

    So-

  86. 17:58

    Oh, oops. How do I get it there? Thank you.

  87. 18:05

    Yeah.

  88. 18:05

    Okay. So when... Let's see. I'm gonna reload it. Looks like this. So if you come here and you don't know what it can do or not, we could just say hi.

  89. 18:17

    Uh, it's gonna be like, "What do you wanna work on Scratch today?" What should I say?

  90. 18:25

    A racing game. I love that. Racing game. Give me

  91. 18:32

    some ideas. Turbo boost button, extra speed. That sounds great. Um, but the cool thing is that it actually integrates with Scratch, so I can go and get, like, any, uh, project from Scratch.

  92. 18:50

    Like, people build really crazy stuff on Scratch. So let's say, like, they're, they build some OCR programs. Uh, this is a bit slow, but people are actually building OCR implementation in Scratch.

  93. 19:02

    Um, and if I find a project that I like, uh, if this works, then I could actually load it in, in my Scratch. I have one that is downloaded, so I'm just gonna load that.

  94. 19:17

    And then let's see. [laughs] So first let's see how it works. Like, I can draw any number here

  95. 19:32

    and then ask it to recognize it. Okay, thinks it's two and eight. Um, but this is a pretty complex program, right? So if I don't know how something works, like, I can actually do a screenshot.

  96. 19:52

    Oh, I did not expect to have two screens. Um, I, I can do a screenshot and then, like, attach it to the chat and it would explain to me what the, what the code in the...

  97. 20:05

    See if I can get it fast enough.

  98. 20:13

    Yeah, I can't get the screenshot from the other tab, but you got the idea. Um, so that's kind of what the program is, and let me go back to this.

  99. 20:25

    And, um, it's free, it's open source. Like I mentioned, there are a lot of new features coming. I hope you can contribute and give us feedback or share it with your y- young friends.

  100. 20:35

    Um, and the reason why this matters is because AI literacy is now actually part of the law. I don't know if you know, but this was passed earlier this month.

  101. 20:45

    It's part of the EU AI Act, and it basically says that all providers and deployers of AI systems should take measures to ensure, to the best of their extent, sufficient level of AI literacy, uh, of their staff, but also of the users of their products, right?

  102. 21:01

    So we need to, in order to ensure this AI literacy, we need to start early, and, um, that's, that's what I'm hoping and trying to do with my work.

  103. 21:10

    Um, if you wanna learn more, uh, there are lots of papers and studies, uh, in, about AI literacy, about AI education, uh, work done on other domains, math misconceptions and science.

  104. 21:22

    It's all on my website. Um, thank you so much. [clapping] [outro music]