Five steps from a connected class to a teacher who can see the learning happen.
Students sign in and connect their school account. CourseWing reads courses, assignments, due dates, announcements, materials, rubrics, grades and teacher feedback. The connection is read-only, and it never asks for Google Drive.
The tutor looks up the student's real course data as it answers and cites its sources under every response. Students can pick a teaching style and edit or delete anything the tutor remembers about them.
Teachers choose Open, Guided or Socratic for the course, then override it per assignment. The server enforces the level on every message, and nothing a student types can raise it.
A receipt records what was practiced, where the student got stuck, and what to reteach, written without quoting the student.
The class pulse, student profiles built from receipts, a review queue for sessions flagged as answer-seeking, and a class assistant that answers questions like "what should I reteach before the unit test?" from summaries.
Built for accuracy first: the tutor answers from the course, and the rules live on the server.
A dedicated sync service pulls each connected course from the Canvas or Google Classroom API on a schedule and indexes assignments, announcements and course files for full-text search, including text extracted from PDFs and documents.
The tutor runs on Claude by Anthropic. Instead of guessing, it calls tools to look up the student's assignments, grades, rubrics and materials at the moment it answers, and it shows which sources it used.
The teacher's help level and the tutoring guidelines are assembled on the server for every turn. A student can't switch them off from the chat.
When a session ends, Claude writes a short structured receipt. The class pulse, student profiles and the class assistant are built from those receipts.
The app runs on Microsoft Azure, and coursewing.org is served by Cloudflare.