Turning recurring Canvas coursework into local AI workflows

The annoying part of Canvas is not always the assignment itself. It is the repeated coordination around the assignment.

Every week, a student checks what is due, finds where the real instructions live, gathers the same kinds of files, explains the same course pattern to an AI tool, reviews the output, and decides what to submit.

Canvas Pilot is my attempt to turn that repeated coordination into a local workflow.

The product is simple at the surface:

scan Canvas -> approval plan -> student approval -> approved workflow -> review-ready output -> REPORT.md

The scan step does not start doing coursework. It writes a plan and stops. The student approves selected work. Only then does Canvas Pilot route the approved items into course-specific workflows.

That is the part I care about: recurring pattern memory.

Canvas MCP servers and Canvas API tools can help an agent access Canvas. They can list assignments, fetch files, inspect modules, and read pages. That is useful, but access is not the same as workflow memory.

A course may always hide the real spec on an external page. Another course may repeat the same reading annotation structure. Another may assign problem sets from the same source every week. If an agent has to rediscover that structure every time, the student is still doing the orchestration.

Canvas Pilot is strongest for AI power users first. If you already know how to operate Codex, Claude Code, or similar local agents, this can remove a large amount of repeated work. Recurring coursework can start to feel close to a one-command workflow: scan, approve, execute, review.

If you do not know how to work with local agents, the current public preview will feel difficult. That is a real boundary.

The project is also local-first. Credentials, cookies, course overlays, real identifiers, runs, assignment inputs, and drafts stay on the user’s machine. The public repository contains the generic framework and public-safe examples.

Canvas Pilot is not a silent homework service and not a hosted no-code app. It is a workflow layer for repeated Canvas coursework.

GitHub: https://github.com/X-isdoingreat/canvas-pilot

Website: https://canvas-pilot.likelyou.com/