Homeschool Families
Parent-led homeschool families who want visible, reviewable AI-assisted instruction and a long-term record of student growth.
OpenTutor connects curriculum, classroom conversation, tutoring, and student work into one parent-supervised learning workflow built around GitHub, AI, and Discord.
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 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 is best treated as an experimental operating model, not a turnkey accredited school package or compliance platform.
OpenTutor uses three layers: GitHub for durable work, Discord for the classroom, and Vibe for guided help.
The system connects records, classroom channels, student work, tutoring, and parent review without hiding the underlying tools.
GitHub holds curriculum, schedules, assignments, revisions, and student portfolios in one reviewable record.
Discord is the daily classroom: subject channels, announcements, check-ins, and study rooms in one familiar space.
Vibe answers inside Discord with explanations, assignment help, quizzes, and next steps under parent oversight.
The model keeps the operating roles clear: Discord hosts the day, GitHub stores the work, Vibe supports instruction, and the parent stays in control.
A small set of transparent tools replaces the usual hidden dashboard.
Assignments, schedules, revisions, and bot behavior leave a trail. GitHub shows what changed; Discord shows the classroom flow.
Students ask in the same place assignments, resources, and family communication already live.
Roles, channels, visible prompt files, and reviewable code keep adults in the operator seat.
Lessons, reading lists, pacing, and projects can be revised like any other versioned work.
Students practice channels, mentions, async check-ins, version history, and digital collaboration early.
Clear questions, documented progress, and versioned work become part of the learning routine.
The repo keeps resources close to the work: assignments, student folders, teacher tools, references, datasets, and useful links.
Shared assignments feed student workspaces; teacher prompts and dashboards keep planning visible.
The learning-center repo separates shared material, student work, teacher tools, and dashboards.
Assignments, references, prompts, and dashboards live in folders adults can inspect and edit.
Each student gets a named workspace for subjects, schedule files, and portfolio work.
Use clear folders like /math, /science, /programming, /history, /reading, and /projects.
Parents curate the library; students use it for subject guides, vocabulary, and references.
Keep formulas, grammar rules, writing frameworks, measurements, history guides, and datasets ready.
Group online tools by purpose so students can find the right aid quickly.
This is a maintained learning library, not a fixed curriculum map.
AI helps turn resources into rubrics, lesson outlines, announcements, 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 classroom tutor and family helper inside OpenTutor. It checks schedules, GitHub files, web results, weather, and family context when the answer depends on them.
Everyday requests should feel like classroom language, not tool commands.
@Vibe what should the students do on Monday?
@Vibe summarize the math folder in the learning center repo.
@Vibe what's the weather in Chicago today?
@Vibe help us turn today's errands and schoolwork into a quick plan.
Vibe combines tutor style, student awareness, recent context, and guardrails so replies fit the classroom.
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.
Vibe explains schoolwork in plain language, adapts to the student, and keeps answers useful without taking over the learning.
Display names, roles, aliases, and recent messages help Vibe distinguish students, parents, and teacher roles in a live Discord thread.
Cooldowns, concise replies, and scoped tools keep Vibe focused on learning and productivity while parents remain the operators.
Daily Flow is a flexible sequence: orient, work, get help, review, build, and close the loop.
Parent posts priorities and links to the right subject folders.
Students know today’s tasks, locations, and expected commits.
Students move through subject folders and assignment materials.
Notes, drafts, and responses land in the right folders.
Vibe rephrases directions, explains concepts, and helps students restart.
Questions become clearer next steps instead of long blockers.
Parent checks completed work, blockers, and afternoon priorities.
Work can be redirected without losing the day’s trail.
Students shift into coding, design, research, or portfolio projects.
Code, websites, drafts, and assets become durable evidence.
Students save finished work, note changes, and identify the next step.
The parent can review completed work and tomorrow’s next actions.
Priorities and expectations start the day.
Subjects, repo materials, and tutor help stay connected.
Finished work and next actions stay visible.
Parents keep authority over curriculum, pacing, permissions, and classroom structure. Vibe supports learning; it does not run the school.
Vibe does not moderate servers or manage classroom permissions.
Prompt rules and skill files stay visible and reviewable.
External access is limited to explicit, reviewable tools.
Students ask in Discord and get help in the flow of class.
The AI can explain and scaffold, but parents set the standards.
Repositories make student work, revisions, and growth visible.
OpenTutor and Vibe are open-source homeschool infrastructure work. 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 Discord bot and signal that the model is worth continuing to build.
Star on GitHubForks make it easier to adapt the bot, test runtime changes, add skills, 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.