Homeschool Families
Parent-led homeschool families who want visible, reviewable AI-assisted instruction and a long-term record of student growth.
OpenTutor v1.0 is the platform. Vibe is the tutor. This page is structured as a design white paper for a parent-operated homeschool system where curriculum lives in repositories, daily instruction lives in Discord, and AI support stays visible, supervised, and accountable.
OpenTutor argues that the next durable model for home education is a supervised learning operating system: one that joins curriculum, communication, tutoring, assessment, and portfolio evidence in a single, reviewable workflow.
This document is written as a working white paper for AI-assisted, parent-supervised education. In this model, GitHub serves as the durable academic record, Discord serves as the live classroom environment, and Vibe (Claude-backed) serves as the on-demand tutor operating inside clear human guardrails.
OpenTutor is designed for communities that want AI support without sacrificing visibility, accountability, or human instructional leadership.
The current release prioritizes operators who are comfortable managing curriculum, communication, and AI tutoring as one connected system rather than a collection of disconnected education apps.
Parent-led homeschool families who want visible, reviewable AI-assisted instruction and a long-term record of student growth.
Microschools, learning pods, independent tutors, and alternative programs coordinating multi-student workflows in lightweight, open infrastructure.
Schools piloting supervised AI, project-based assessment, and portfolio-driven documentation before larger institutional adoption.
OpenTutor v1.0 is best treated as an experimental operating model, not a turnkey accredited school package or compliance platform.
OpenTutor separates the homeschool stack into three layers so each tool can do one job well without turning the family workflow into enterprise software.
GitHub becomes the source of truth for the school itself. Curriculum can live in subject repositories, the weekly calendar can live in a schedule repo, and each student can build a visible portfolio of writing, projects, revisions, and progress over time.
Discord is the daily interface. Subject channels, announcements, office hours, assignment check-ins, and quiet study rooms give kids one place to ask questions, receive direction, and stay connected to the rhythm of the day.
Vibe sits inside Discord and is backed by Claude to explain concepts, break down assignments, quiz students, rephrase directions, and help a stuck learner keep moving without leaving the supervised classroom environment.
The model is simple on purpose: Discord is the classroom center, GitHub holds the work, Vibe supports instruction, and the parent remains the operator.
Discord sits at the center of the school day, supported by GitHub structure, tutor assistance, and visible parent oversight.
One live classroom surface, one parent operator, one curriculum layer, and one tutor layer work together without hiding how the system is actually implemented.
Assignments, revisions, schedules, and bot behavior can all be tracked. GitHub history shows what changed and when. Discord logs show what happened in the classroom. That makes it easier to see effort, growth, and gaps without relying on memory.
Kids do not need to bounce between separate portals for answers. They can ask in the same channel where the assignment was posted, where the resources live, and where the family already communicates. That reduces friction and keeps attention on the task.
Claude-backed tutoring is useful because it is immediate, but the system still keeps the parent in control. Roles, channels, moderation tools, and logs make the adult the operator of the environment rather than handing that control to a black box.
Homeschool plans change. Lessons get improved, reading lists get swapped, pacing shifts, and projects get refined. Storing the school in repositories makes the curriculum editable, reusable, and easier to improve semester after semester.
Discord, Teams, Slack, GitHub, channels, mentions, async check-ins, repository hygiene, and digital collaboration are not side benefits. They are core forms of literacy for modern digital work, and students can start learning them early in a supervised environment.
Instead of learning only isolated subjects, students also learn how to communicate in channels, document progress, manage versioned work, ask clear questions, and move projects forward using the same patterns they are likely to see later in technical, creative, or corporate settings.
The OpenTutor repo already shows what the homeschool side can look like in practice: assignments, resources, student folders, teacher dashboards, and AI prompt files all live in a visible structure that families can edit directly.
The live open-tutor structure separates shared materials, student workspaces, and teacher tools so the system stays readable as it grows.
Teachers can build from actual directories like assignment packs, reference guides, AI assistant prompts, and site dashboards instead of relying on hidden platform menus.
Students can have a named workspace with grade-level subjects, a schedule file, and a README hub so daily work and long-term portfolio pieces stay in one place.
This section is a shared resource-folder model, not a curriculum chart. It shows how parents can organize educational materials, reference documents, datasets, and useful links so students have one supervised place to read, watch, review, and build from.
Organize clear subfolders like /math, /science, /programming, /history, /reading, and /projects.
Parents curate the library, monitor progress, and keep resources appropriate. Students check it regularly for subject cheat sheets, step-by-step skill guides, and vocabulary lists by grade without changing shared materials.
Keep practical cheat sheets ready: formulas, grammar rules, writing frameworks, measurements, world facts, finance, physics, chemistry, U.S. basics, and history guides.
Store reusable CSV and JSON datasets for projects, coding, analysis, and research. Group online tools by purpose, not brand.
This is a maintained learning library, not a fixed curriculum map.
Parents and teachers curate it. AI helps turn it into rubric templates, lesson plan outlines, ready-to-post Discord announcements, assignment prompts, assessment banks, worksheets, and review materials.
OpenTutor depends on a few real-world setup steps. These official links make it easier to stand the system up without guesswork, then layer in agentic coding workflows where the parent stays in the loop as curriculum architect, assignment maintainer, and feedback lead.
Parents and students should have real GitHub accounts so assignments, commits, and project history map to actual people.
Discord becomes the day-to-day classroom layer, so the main job is creating a clean server with obvious subject and admin spaces.
Create the Discord application, install the bot with limited scopes, then run the repo with the correct bot token and Anthropic key.
Agentic coding tools can reduce friction across assignments, documents, and projects. Parents keep human oversight while using Codex-style agents to draft curricula, generate differentiated tasks, score with rubrics, and produce actionable feedback faster.
Vibe is the friendly tutor persona inside OpenTutor. Its behavior is not marketing copy; it is defined directly in the Python bot code and designed for concise, encouraging, middle-school support inside Discord.
Subject channels, prompts, and tutor help live in the same classroom flow, so support appears where students are already working.
Recent context, speaker awareness, concise replies, and guardrails turn tutoring into a practical classroom layer instead of a generic chat window.
The system prompt explicitly positions Vibe as educational, encouraging, and good at making complex middle-school topics easy to understand without overexplaining.
It keeps up to 10 recent message pairs per channel, which means follow-up questions can build on what a student already asked instead of restarting every time.
User display names, roles, and mention targets are injected into the model context, so Vibe can interpret classroom conversations with much better situational awareness.
Students only need to @mention Vibe in a subject channel. That keeps tutoring lightweight and makes it easy to ask for help the moment confusion happens.
If a response gets too long for Discord, the bot automatically splits it into clean message chunks. That keeps explanations readable without breaking the conversation flow.
A built-in cooldown limits spam, destructive actions are restricted to the Admin role, and admin actions are logged to #bot-logs for transparent supervision.
A useful homeschool platform has to describe the actual shape of a day. This version is organized as a flexible sequence rather than a clock-based schedule.
The day opens in Discord with the parent’s framing note, priorities, and links to the correct subject folders. Students learn to locate the day’s work, pull current assignments, and understand the shape of the day before they begin.
Students start with a clean view of the day’s tasks, the correct repository locations, and the expectations for what will be committed back later.
Students work through their subject folders and assignment materials directly. Because each child’s structure is organized by subject, the flow stays predictable even when assignments vary in type or depth.
Responses, notes, worksheets, and drafts begin accumulating inside the correct subject and assignment folders instead of being scattered across devices.
When confusion appears, Vibe can rephrase directions, explain a middle-school concept, or help a student recover momentum. The parent stays in control while the tutor reduces waiting and frustration.
Students learn to ask clearer questions, use async help responsibly, and keep moving instead of stalling out on one blocker for half the day.
The parent can quickly review what has been completed, what is blocked, and which folders or subjects need attention in the afternoon. This turns the repository structure into a practical management surface.
Students see that progress is measurable, revisions are normal, and work can be redirected without losing the trail of what happened earlier in the day.
The afternoon expands beyond assignment completion into project folders for coding, design, research, and portfolio work. This is where students practice making things, not just finishing prompts.
Code, websites, creative assets, and project drafts accumulate as durable evidence of skill. Students learn that commits can represent real shipped work, not only homework responses.
The day ends with students committing finished assignment work back into the correct folders, noting what changed, and identifying what should happen next. The routine reinforces documentation, ownership, and continuity.
The result is a visible trail of completed assignments, active projects, and next actions that can be reviewed by the parent and revisited by the student tomorrow.
Orientation, clarity, and visible expectations establish the day before work begins.
Subject channels, repository materials, and lightweight tutor support stay connected during focused work.
Finished work gets committed back into GitHub, and end-of-day review makes progress visible and easier to improve the next day.
The tutor layer only makes sense in a homeschool setting when parents retain authority over permissions, logs, discipline, and classroom structure.
Parents can manage the server directly through Vibe. Kick, ban, timeout, or clean up disruptive activity with admin-gated commands instead of digging through Discord menus mid-lesson.
Administrative actions are logged to #bot-logs, creating a clear audit trail for moderation and server changes. Parents can review how the classroom is being managed instead of relying on invisible automation.
Need a new room for algebra, writing workshop, science lab, or project review? Vibe can help set up organized channels so each subject has a dedicated place for materials, questions, and discussion.
Students ask for help by tagging the bot in the exact study space they are already using. That makes tutoring feel like part of the classroom workflow instead of a separate app they have to learn.
Claude gives explanations, examples, and scaffolding, but the parent still decides the curriculum, the pace, and the standards. The bot supports instruction; it does not become the school.
Because student work can live in repositories, the output of learning becomes visible: essays, notes, code, research, revisions, and project artifacts that show how understanding develops over time.
OpenTutor is an open-source homeschool infrastructure project. GitHub stars and forks help people discover, test, and improve the project; donations can fund API costs, curriculum maintenance, documentation, and continued development.
Stars help more parents and educators find the project and signal that the model is worth continuing to build.
Star on GitHubForks make it easier to adapt the model, test curriculum changes, and send improvements back through pull requests.
Fork on GitHubDirect Bitcoin support for OpenTutor infrastructure, hosting, and ongoing development.
Direct EVM-compatible support for OpenTutor infrastructure, tooling, and documentation work.
These addresses fund OpenTutor infrastructure, API usage, curriculum maintenance, and continued development.