ChalkBack is a local-first B2B digital teaching assistant built on Screenpipe, designed to eliminate the tedious post-class routine of reviewing, gap-checking, and drafting exercises.
Operating quietly on the teacher's device, Screenpipe passively captures classroom audio and on-screen slides. Right after class, an automated AI agent accesses this context in read-only mode to perform four tasks: mapping delivered content to syllabus benchmarks, pinpointing missed topics across past weeks, learning the teacher’s specific assessment style, and generating sourced quizzes and interactive mini-games.
Privacy and teacher control remain paramount: raw audio and screen recordings never leave the local machine. Teachers retain full approval over all generated materials, and only high-level syllabus coverage data is shared with the department dashboard. Deployed across entire schools with a single command, ChalkBack delivers a uniquely personalized assistant to every educator while giving administrators real-time visibility into curriculum pacing and early warnings.
ChalkBack uses screenpipe as the teacher's local classroom memory, through its REST API on localhost:3030. The teacher console(FastAPI, localhost:4000) checks screenpipe's health and audio devices, and starts or stops capture with POST /audio/start and /audio/stop. Each request is authenticated with the local API key.
When recording stops, the console runs chalkback-pipe, a screenpipe pipe, with npx screenpipe pipe run. The pipe has read-only permissions: it may call only GET /search, /health and /notify, and it is denied access to sensitive apps and private browser windows. It pulls the microphone transcript and the slide text (accessibility/OCR) for the lesson’s time window, then aligns them into teaching segments by timestamp. An AI agent maps each segment to the syllabus knowledge points, compares the result with the lesson plan, and writes coverage, missed-topic alerts and a quiz that cites its source to a local outbox.
Raw transcripts, screenshots and screenpipe IDs never leave the laptop. Only an approved coverage summary is sent to the school Hub, and the Hub validates it against a JSON schema before accepting it.