scratchfoundation / scratchfoundation/scratch-editor

Agentic coding support?

Open
#623 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
281
Forks
276
Avg merge
7d 8h
Merged PRs (30d)
6

Description

tl;dr: are you guys open to adding a cursor-like agentic coding pane (along with something like an LSP to support it)? If this already exists, I'm super sorry and would love a pointer!

My 9yo son is attending a coding camp again. I was speaking to him about his experience and learned that most of the kids spent their time googling and downloading games that other people had already developed. I asked him "but you must have ideas about how you'd like to change these games or tweak them, right?" and while he agreed, he said that it was "too much work". While part of me is sad that my kid is just not interested in learning the mechanics of coding, the other part of me recognizes that I haven't directly authored a single line of code in well over 6 months if not a year. And yet my productivity is roughly 10x and climbing, my code quality is up, test coverage up, etc. So... thoughts about adding agentic coding support?

The rather immediate counter argument, about "that's not how you learn to code" strikes me as enshrining the artisanship while underplaying the critical thinking aspect, which, at least for me, is brought to the fore by agentic coding work. I think this is one way to get kids experimenting, encourage and support curiosity, and I think that's a gateway to learning.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by mapping the JavaScript mono-repo’s editor architecture and checking whether an LSP or agentic integration already exists; define the coding pane, integration boundary, and acceptance criteria before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
ai, developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.