Planned nothing on this page exists yet
A classroom is a room, too.
A plan for bringing the smart development environment (SDE) to middle school and up: lesson planning, step-by-step assignments, help for a student who is stuck, and knowledge checks, with the teacher in charge. A plan, not a product.
- No classroom features exist today. There is no sign-up, no waitlist, no pricing and no school pilot, and no school uses VESPR.
- Written October 29, 2026 from the product plan. How we intend to treat students and children is on Children and schools.
what exists today
Three things we already have would be the base.
Who wrote it
Every character records who wrote it, a person or an agent, and shows it on hover. Next to a student’s own work, that is a plain record of what the agent did.
History and replay
A History of what was done (edits, runs, approvals) and a replay of a session.
A tutoring skill
A small text skill called tutor-mode tells the agent to ask a question first and give a hint instead of the answer. It is a set of instructions, not a mode: there is no hint counter, no teacher view and no limits for students.
the plan
What a teacher would get.
Team and Kids tabs Planned
Team: colleagues and administrators, shared lesson banks and department approvals. Kids: the class roster, assignments, each student’s progress, who is stuck, how many hints each student used, and each student’s own work next to what the agent wrote. Students would sign in through the school (Clever is the planned route), one login per student. Behind both tabs is a hierarchy: school or department, then class or team, then person.
Lesson planner Planned
The teacher describes the lesson: topic, grade band, minutes, what students already know and, optionally, standards. The planner drafts objectives, a warm-up, instruction, guided and independent practice, a check for understanding, differentiation and materials, and a slide deck. The teacher edits all of it before anything reaches students.
Step-by-step assignments Planned
The planner breaks a project into steps. Each step has a goal, starter code, a test that shows pass or fail, and a ladder of help: a question, then a nudge, then a hint, and a worked example only after a number of tries the teacher sets.
Help for a student who is lost Planned
A tutor setting of the agent that asks questions instead of giving answers, runs the student’s own tests to show results, and does not write into the student’s files unless asked. A stuck detector notices when the same test keeps failing or nothing has been edited for a set time, offers help to the student and lets the teacher know.
Knowledge checks Planned
Quick checks made from the lesson or the assignment: multiple choice (graded automatically), short answer, predict the output, read the code and find the bug. Each comes with an answer key and a rubric, and the teacher reviews and edits a check before it is published. Reading-level and accessibility options are part of the plan.
Safe blocks, and what teachers can see Planned
Locked files a student cannot change, no internet for commands, and run and AI-token limits per student, set by the teacher or school. Teachers could see a student’s conversations with the agent, and students would be told so on screen. There would be no hidden monitoring.
what has to happen first
Before any school sees this.
- Counsel reviews how student data is handled before any school pilot. Nothing on this page is a claim of compliance with any student-privacy law.
- The security gaps that matter for students are closed. Today anyone with a token can reach every workspace on a server, and the agent’s sandbox shares its secrets. See Security.
- School sign-in through Clever needs Clever’s approval and written agreements with schools.
- The classroom features are built and tested with teachers.
Related: VESPR for teams shares the same planned foundation (a hierarchy, rules about what each level may do, an audit log).